Hi All:
As requested, I would like to introduce myself as a representative of Microsoft Azure and request membership in the CentOS Cloud Instance SIG. My formal goal in joining this group is of course to bring community-supported and high-quality CentOS images to Microsoft Azure. At Microsoft I drive the technical collaboration with many of the various Linux distributions that exist in the Azure Gallery - which includes numerous efforts around image creation, testing and support of these images on Azure. I hope to do the same with the CentOS community.
My group is also responsible for a few other key components that will be important for this effort, such as the device drivers for Hyper-V/Azure (which already ship with the CentOS kernel), the Azure Linux agent and various others. We work closely with the upstream developers to ensure customers have a great experience running CentOS in Hyper-V/Azure virtualized environments. Having official CentOS images I think will allow us to build and continue to improve on those efforts.
Looking forward to working with you all. Please let me know if I should provide more details.
Thanks! Steve
Welcome!
On 10/26/2015 05:44 PM, Stephen Zarkos wrote:
Hi All:
As requested, I would like to introduce myself as a representative of Microsoft Azure and request membership in the CentOS Cloud Instance SIG. My formal goal in joining this group is of course to bring community-supported and high-quality CentOS images to Microsoft Azure. At Microsoft I drive the technical collaboration with many of the various Linux distributions that exist in the Azure Gallery - which includes numerous efforts around image creation, testing and support of these images on Azure. I hope to do the same with the CentOS community.
My group is also responsible for a few other key components that will be important for this effort, such as the device drivers for Hyper-V/Azure (which already ship with the CentOS kernel), the Azure Linux agent and various others. We work closely with the upstream developers to ensure customers have a great experience running CentOS in Hyper-V/Azure virtualized environments. Having official CentOS images I think will allow us to build and continue to improve on those efforts.
Looking forward to working with you all. Please let me know if I should provide more details.
Thanks! Steve
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Welcome Steve
Best Regards,
*Sandeep L Khuperkar | Director*
Mobile : +91-9987536436
Skype id : khuperkar
*ASHNIK TECHNOLOGY SOLUTIONS PVT. LTD.*
#711, Dhamji Shamji Business Galleria, LBS Marg, Kanjurmarg, Mumbai - 400078
India | www.ashnik.com
*[image: icons]*
[image: www.ashnik.com] http://www.ashnik.com/
On Wed, Oct 28, 2015 at 9:35 PM, Jim Perrin jperrin@centos.org wrote:
Welcome!
On 10/26/2015 05:44 PM, Stephen Zarkos wrote:
Hi All:
As requested, I would like to introduce myself as a representative of
Microsoft Azure and request membership in the CentOS Cloud Instance SIG. My formal goal in joining this group is of course to bring community-supported and high-quality CentOS images to Microsoft Azure. At Microsoft I drive the technical collaboration with many of the various Linux distributions that exist in the Azure Gallery - which includes numerous efforts around image creation, testing and support of these images on Azure. I hope to do the same with the CentOS community.
My group is also responsible for a few other key components that will be
important for this effort, such as the device drivers for Hyper-V/Azure (which already ship with the CentOS kernel), the Azure Linux agent and various others. We work closely with the upstream developers to ensure customers have a great experience running CentOS in Hyper-V/Azure virtualized environments. Having official CentOS images I think will allow us to build and continue to improve on those efforts.
Looking forward to working with you all. Please let me know if I should
provide more details.
Thanks! Steve
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 26/10/15 22:44, Stephen Zarkos wrote:
Hi All:
As requested, I would like to introduce myself as a representative of Microsoft Azure and request membership in the CentOS Cloud Instance SIG. My formal goal in joining this group is of course to bring community-supported and high-quality CentOS images to Microsoft Azure. At Microsoft I drive the technical collaboration with many of the various Linux distributions that exist in the Azure Gallery - which includes numerous efforts around image creation, testing and support of these images on Azure. I hope to do the same with the CentOS community.
My group is also responsible for a few other key components that will be important for this effort, such as the device drivers for Hyper-V/Azure (which already ship with the CentOS kernel), the Azure Linux agent and various others. We work closely with the upstream developers to ensure customers have a great experience running CentOS in Hyper-V/Azure virtualized environments. Having official CentOS images I think will allow us to build and continue to improve on those efforts.
Looking forward to working with you all. Please let me know if I should provide more details.
thanks for reaching out, and I look forward to working with you on this.
Going by your email, am I correct in assuming that the hyper-v and azure images would be identical ?
And I guess the next step here would be to get you signed up on the SIG ( I will work on that ), and start looking at the Azure Linux agent and how best to get that built in cbs.centos.org
Aside from this, can you potentially list our the steps needed to adapt http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 ? We can then roll those changes in and look at testing the image. If there are changes that might impact other consumers of the image, we can do an Azure branded image ( which might also work out better for folks looking at BYOI process' ).
regards,
Hi,
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel- bounces@centos.org] On Behalf Of Karanbir Singh Sent: Wednesday, November 4, 2015 5:19 AM To: centos-devel@centos.org Subject: Re: [CentOS-devel] Request to join the Cloud Instance SIG for Microsoft Azure
On 26/10/15 22:44, Stephen Zarkos wrote:
Hi All:
Looking forward to working with you all. Please let me know if I should
provide more details.
thanks for reaching out, and I look forward to working with you on this.
Going by your email, am I correct in assuming that the hyper-v and azure images would be identical ?
They could be, although it may be better to build these separately for now and see how we can merge them later. For example, the Hyper-V images would not require the Azure Linux agent, and we may wish to enable additional userspace daemons to handle specific on-prem Hyper-V scenarios (VSS for snapshotting, fcopy, etc.).
Overall the existence of the agent or services will not adversely impact the VM if it's running in either environment (the agent may just add a bit of noise in the console logs when running on-prem).
And I guess the next step here would be to get you signed up on the SIG ( I will work on that ), and start looking at the Azure Linux agent and how best to get that built in
Currently the Linux agent is available in EPEL, if that helps. We may work to integrate it with upstream RHEL, but that's not the case today.
Aside from this, can you potentially list our the steps needed to adapt http%3a%2f%2fcloud.ce ntos.org%2fcentos%2f7%2fimages%2fCentOS-7-x86_64- GenericCloud.qcow2 ? We can then roll those changes in and look at testing the image. If there are changes that might impact other consumers of the image, we can do an Azure branded image ( which might also work out better for folks looking at BYOI process' ).
Sure, I can list the steps here. Is there a wiki or similar available where we can codify these steps?
There are only a few changes:
1) Add the following parameters to /etc/default/grub:
earlyprintk=ttyS0,115200 rootdelay=300
1a) We'd also recommend removing "crashkernel=auto" as well. This parameter often won't work right on Hyper-V without some additional tweaks anyway, and will save memory on smaller VM sizes (i.e. Azure's A0 size).
1b) Be sure to rebuild grub.cfg (grub2-mkconfig -o /boot/grub2/grub.cfg)
2) Remove the "cloud-init" package. The Azure datasource does not quite work in CentOS yet.
3) Install WALinuxAgent package from EPEL:
rpm -ivh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm yum -y install WALinuxAgent systemctl enable waagent.service
4) Enable NTP (timedatectl set-ntp true)
5) Clear the file "/lib/udev/rules.d/75-persistent-net-generator.rules". MAC addresses can change. - Note that this step may not be required in the future.
Our team can help test the image once it's built. Please let me know if you have questions.
Thanks! Steve
Hi,
On 12/11/15 21:41, Stephen Zarkos wrote:
Going by your email, am I correct in assuming that the hyper-v and azure images would be identical ?
They could be, although it may be better to build these separately for now and see how we can merge them later. For example, the Hyper-V images would not require the Azure Linux agent, and we may wish to enable additional userspace daemons to handle specific on-prem Hyper-V scenarios (VSS for snapshotting, fcopy, etc.).
okay, lets do the Azure ones first in that case.
Overall the existence of the agent or services will not adversely impact the VM if it's running in either environment (the agent may just add a bit of noise in the console logs when running on-prem).
we seem to have inherited https://git.centos.org/summary/rpms!WALinuxAgent which maybe a good place to start from ( I'm going to check if we need some rebranding / debranding around it as well ).
And I guess the next step here would be to get you signed up on the SIG ( I will work on that ), and start looking at the Azure Linux agent and how best to get that built in
Currently the Linux agent is available in EPEL, if that helps. We may work to integrate it with upstream RHEL, but that's not the case today.
Aside from this, can you potentially list our the steps needed to adapt http%3a%2f%2fcloud.ce ntos.org%2fcentos%2f7%2fimages%2fCentOS-7-x86_64- GenericCloud.qcow2 ? We can then roll those changes in and look at testing the image. If there are changes that might impact other consumers of the image, we can do an Azure branded image ( which might also work out better for folks looking at BYOI process' ).
Sure, I can list the steps here. Is there a wiki or similar available where we can codify these steps?
There are only a few changes:
Add the following parameters to /etc/default/grub:
earlyprintk=ttyS0,115200 rootdelay=3001a) We'd also recommend removing "crashkernel=auto" as well. This parameter often won't work right on Hyper-V without some additional tweaks anyway, and will save memory on smaller VM sizes (i.e. Azure's A0 size).
1b) Be sure to rebuild grub.cfg (grub2-mkconfig -o /boot/grub2/grub.cfg)
Remove the "cloud-init" package. The Azure datasource does not quite work in CentOS yet.
Install WALinuxAgent package from EPEL:
rpm -ivh http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm yum -y install WALinuxAgent systemctl enable waagent.service
Enable NTP (timedatectl set-ntp true)
Clear the file "/lib/udev/rules.d/75-persistent-net-generator.rules". MAC addresses can change.
- Note that this step may not be required in the future.
Our team can help test the image once it's built. Please let me know if you have questions.
I'll get a baseline image up in the next few days and we can try it out. It will all end up in a git repo, so we can collaborate from there.
-
Jim Perrin -
Karanbir Singh -
Sandeep Khuperkar -
Stephen Zarkos