settingsLogin | Registersettings

[Openstack-operators] Gentoo image availability

0 votes

Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,

--
Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

asked Jun 8, 2015 in openstack-operators by prometheanfire_at_ge (6,880 points)   1 4 5

12 Responses

0 votes

Since these are distro packages, you might be interested in converting the prep scripts
into a DIB (diskimage-builder) element. We can presently build images for Debian/Ubuntu/Centos/Fedora/RHEL/openSUSE...
I'm sure someone out there would appreciate having gentoo, too.

On Jun 8, 2015, at 8:26 AM, Matthew Thode prometheanfire@gentoo.org wrote:

Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,

--
Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

responded Jun 8, 2015 by Abel_Lopez (4,820 points)   1 3 5
0 votes

Nice to hear.

You're doing a great job!

Few things to make Gentoo 'first class citizen' for openstack (guest).

  1. Check if you supports for all eth's, not only eth0. If instance boots
    with two or more interfaces, it should be able to get all it addresses.

  2. Add Gentoo 'element' to disk-image-builder
    (https://github.com/openstack/diskimage-builder)

  3. Ship image with proper cloud-init cloud.cfg

On 06/08/2015 06:26 PM, Matthew Thode wrote:
Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 9, 2015 by George_Shuklin (4,720 points)   1 9 12
0 votes

On 06/08/2015 09:17 PM, George Shuklin wrote:
Nice to hear.

You're doing a great job!

Few things to make Gentoo 'first class citizen' for openstack (guest).

  1. Check if you supports for all eth's, not only eth0. If instance boots
    with two or more interfaces, it should be able to get all it addresses.

  2. Add Gentoo 'element' to disk-image-builder
    (https://github.com/openstack/diskimage-builder)

  3. Ship image with proper cloud-init cloud.cfg

On 06/08/2015 06:26 PM, Matthew Thode wrote:

Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Ya, not sure how to do multi-interface yet. I'd love if the cloud-init
static ip support would work with it. (hash with macs being the key and
a list of IPs being the value for each interface). Then dhcp can go
away (I tend to much prefer config-drive).

The disk-image-builder support is on my todo list already :D

I just updated the cloud-init ebuild with a better cloud.cfg, could
probably use more love, but it works.

I am working on getting gentoo as a first class citizen in
openstack-ansible as well, which depends on the disk-image-builder work.
So much work still to do :D

--
Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 9, 2015 by prometheanfire_at_ge (6,880 points)   1 4 5
0 votes

Awesome. Are they ready enough that they should go into the app catalog? (http://apps.openstack.org)

Thanks,
Kevin


From: Matthew Thode [prometheanfire@gentoo.org]
Sent: Monday, June 08, 2015 8:26 AM
To: openstack-operators@lists.openstack.org
Subject: [Openstack-operators] Gentoo image availability

Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,

--
Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 9, 2015 by Fox,_Kevin_M (29,360 points)   1 3 4
0 votes

On 06/09/2015 10:34 AM, Fox, Kevin M wrote:
Awesome. Are they ready enough that they should go into the app catalog? (http://apps.openstack.org)

Thanks,
Kevin


From: Matthew Thode [prometheanfire@gentoo.org]
Sent: Monday, June 08, 2015 8:26 AM
To: openstack-operators@lists.openstack.org
Subject: [Openstack-operators] Gentoo image availability

Hi,

I'm the packager of Openstack on Gentoo and have just started generation
of Gentoo Openstack images. Right now it is just a basic amd64 image,
but I plan on adding nomultilib and hardened variants (for a total of at
least 4 images). I plan on generating these images at least weekly

These images are not yet sanctioned by our infra team, but I plan on
remedying that (being a member of said team should help).

I am currently using the scripts at
https://github.com/prometheanfire/gentoo-cloud-prep to generate the
images (based on a heavily modified version of Matt Vandermeulen's
scripts). If you have any issues please submit bugs there or contact me
on irc (prometheanfire on freenode).

Here's the link to the images, I'm currently gpg signing them with the
same key I use to sign this email (offline master key smartcard setup
for security minded folk).

http://23.253.251.73/

Let me know if you have questions,

--
Matthew Thode (prometheanfire)

It could probably go into the catalog, but I'd rather get it generated
and signed by our (gentoo's) infra first.

--
-- Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

responded Jun 9, 2015 by prometheanfire_at_ge (6,880 points)   1 4 5
0 votes

On 06/09/2015 05:46 AM, Matthew Thode wrote:

Ya, not sure how to do multi-interface yet. I'd love if the cloud-init
static ip support would work with it. (hash with macs being the key and
a list of IPs being the value for each interface). Then dhcp can go
away (I tend to much prefer config-drive).

The disk-image-builder support is on my todo list already :D

I just updated the cloud-init ebuild with a better cloud.cfg, could
probably use more love, but it works.

I am working on getting gentoo as a first class citizen in
openstack-ansible as well, which depends on the disk-image-builder work.
So much work still to do :D

Aw. Don't discriminate DHCP. It has many nice features (for example, if
you add new interface to existing VM, cloud-init with static config will
ignore it, but DHCP will works like magic).

I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for
all interfaces but eth0 allows to support most of the future interfaces.
Same for CentOS - you can add few eth scripts to network configuration
and they will works as soon as new interface appears.


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 9, 2015 by George_Shuklin (4,720 points)   1 9 12
0 votes

This has been one thing about config-drive that has bothered me for a
while now. I don¹t see why config-drive can't be recreated when the
metadata about the VM is changed. This created once and only once thing
doesn't make a whole lot of sense to me. At a minimum you could re-create
config drive on the stop/start of the vm.

This would also solve the live migration doesn't work for vm's with
config-drive, instead of relying on libvirt to migrate the cdrom file - we
could just rebuild it with the information that we have (since it was
generated with the information that we have to begin with)


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.

On 6/9/15, 5:14 PM, "George Shuklin" george.shuklin@gmail.com wrote:

On 06/09/2015 05:46 AM, Matthew Thode wrote:

Ya, not sure how to do multi-interface yet. I'd love if the cloud-init
static ip support would work with it. (hash with macs being the key and
a list of IPs being the value for each interface). Then dhcp can go
away (I tend to much prefer config-drive).

The disk-image-builder support is on my todo list already :D

I just updated the cloud-init ebuild with a better cloud.cfg, could
probably use more love, but it works.

I am working on getting gentoo as a first class citizen in
openstack-ansible as well, which depends on the disk-image-builder work.
So much work still to do :D

Aw. Don't discriminate DHCP. It has many nice features (for example, if
you add new interface to existing VM, cloud-init with static config will
ignore it, but DHCP will works like magic).

I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for
all interfaces but eth0 allows to support most of the future interfaces.
Same for CentOS - you can add few eth scripts to network configuration
and they will works as soon as new interface appears.


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 9, 2015 by Kris_G._Lindgren (7,740 points)   1 6 10
0 votes

On 10-06-2015 02:14, George Shuklin wrote:
Aw. Don't discriminate DHCP. It has many nice features (for example, if you add
new interface to existing VM, cloud-init with static config will ignore it, but
DHCP will works like magic).

I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all
interfaces but eth0 allows to support most of the future interfaces. Same for
CentOS - you can add few eth scripts to network configuration and they will
works as soon as new interface appears.

I want to add to this comment. I believe this hot-plug feature for ethernet
devices is essential in the cloud environment. Short time ago I needed to move
port from one instance to another while keeping the internal IP address same. I
achieved it by removing a port from the old instance, re-creating the port with
the same ip address, and pluging it to the new instance.

The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) and
the ip addresses were distributed using DHCP. When the interface was
re-plugged, dhclient requested an ip address and the DHCP server gave the
internal address of the port which I specified.

So, it would be really great if you can support hot-plugging for ethernet
devices and DHCP. I find them very useful and I believe many people would
expect this feature from Gentoo image.

Regards,

--
Eren Türkay, System Administrator
https://skyatlas.com/ | +90 850 885 0357

Yildiz Teknik Universitesi Davutpasa Kampusu
Teknopark Bolgesi, D2 Blok No:107
Esenler, Istanbul Pk.34220


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

responded Jun 11, 2015 by Eren_Türkay (1,220 points)   1 4 8
0 votes

On 06/11/2015 04:11 AM, Eren Türkay wrote:
On 10-06-2015 02:14, George Shuklin wrote:

Aw. Don't discriminate DHCP. It has many nice features (for example, if you add
new interface to existing VM, cloud-init with static config will ignore it, but
DHCP will works like magic).

I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all
interfaces but eth0 allows to support most of the future interfaces. Same for
CentOS - you can add few eth scripts to network configuration and they will
works as soon as new interface appears.

I want to add to this comment. I believe this hot-plug feature for ethernet
devices is essential in the cloud environment. Short time ago I needed to move
port from one instance to another while keeping the internal IP address same. I
achieved it by removing a port from the old instance, re-creating the port with
the same ip address, and pluging it to the new instance.

The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) and
the ip addresses were distributed using DHCP. When the interface was
re-plugged, dhclient requested an ip address and the DHCP server gave the
internal address of the port which I specified.

So, it would be really great if you can support hot-plugging for ethernet
devices and DHCP. I find them very useful and I believe many people would
expect this feature from Gentoo image.

Regards,


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

ya, it's probably the number one thing I want to see as well and the
next thing I'm working on.

--
Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

responded Jun 11, 2015 by prometheanfire_at_ge (6,880 points)   1 4 5
0 votes

On 06/11/2015 10:12 AM, Matthew Thode wrote:
On 06/11/2015 04:11 AM, Eren Türkay wrote:

On 10-06-2015 02:14, George Shuklin wrote:

Aw. Don't discriminate DHCP. It has many nice features (for example, if you add
new interface to existing VM, cloud-init with static config will ignore it, but
DHCP will works like magic).

I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all
interfaces but eth0 allows to support most of the future interfaces. Same for
CentOS - you can add few eth scripts to network configuration and they will
works as soon as new interface appears.

I want to add to this comment. I believe this hot-plug feature for ethernet
devices is essential in the cloud environment. Short time ago I needed to move
port from one instance to another while keeping the internal IP address same. I
achieved it by removing a port from the old instance, re-creating the port with
the same ip address, and pluging it to the new instance.

The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) and
the ip addresses were distributed using DHCP. When the interface was
re-plugged, dhclient requested an ip address and the DHCP server gave the
internal address of the port which I specified.

So, it would be really great if you can support hot-plugging for ethernet
devices and DHCP. I find them very useful and I believe many people would
expect this feature from Gentoo image.

Regards,


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

ya, it's probably the number one thing I want to see as well and the
next thing I'm working on.


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

ok, updated the images. Did the following.

  1. Allowed for any interface to get auto addressed (dhcpcd handles that
    actually, no net configs needed).

  2. The rootfs resizes on first boot now.

  3. image size is reduced.

  4. more profiles are now available.

Notes... DIB is on my todo, but should be very minor, since I'm
generating more or less official openstack stage4 guest tarballs
already. Also, getting these images themselves official (within gentoo)
is next and kinda hard if only because it needs to be totally within
catalyst.

--
-- Matthew Thode (prometheanfire)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

responded Jun 23, 2015 by prometheanfire_at_ge (6,880 points)   1 4 5
...