Re: [Openstack-operators] [dnsmasq] setting ntp-server

2017-08-18 Thread Carlos Konstanski
was not being wired correctly. Packets were not making it to the qr device. Not sure why. But with an IP address, everything works and a /var/lib/ntp/ntp.conf.dhcp gets written. As long as the /etc/init.d/ntp script looks for this file, everything is golden. Carlos Carlos Konstanski writes: >

[Openstack-operators] [dnsmasq] setting ntp-server

2017-08-18 Thread Carlos Konstanski
openstack to configure dnsmasq thusly. There are two possibilities: a neutron config option or the overriding of the entire dnsmasq.conf. The former would be mch simpler and less messy. Is there such a setting in neutron.conf? Carlos Konstanski ___

[Openstack-operators] [nova] Obtaining nova settings at runtime

2017-06-14 Thread Carlos Konstanski
Is there a way to obtain nova configuration settings at runtime without resorting to SSHing onto the compute host and greping nova.conf? For instance a CLI call? At the moment I'm looking at cpu_allocation_ratio and ram_allocation_ratio. There may be more along this vein. Alles Gute, C

Re: [Openstack-operators] [nova] instance partition size discrepancy

2017-04-26 Thread Carlos Konstanski
natively, if you use images with cloud-init and > initramfs-growroot installed, it should work out of the box. > Tomas > > -Original Message- > From: Carlos Konstanski [mailto:ckonstan...@pippiandcarlos.com] > Sent: Wednesday, April 26, 2017 12:02 AM > To: openstac

[Openstack-operators] [nova] instance partition size discrepancy

2017-04-25 Thread Carlos Konstanski
/show/eNt8nLNLhHAL5OYICqbs/ Notice that everything shows the size as 20 GB except df, which shows it as 2.8 GB. I ran the previous instance out of space before spinning up this new one, so 2.8 seems to be the winner (though wrong). Figured I'd check to see if this is a known issue while I dig deepe

Re: [Openstack-operators] [openstack-operators] [nova] cloud.cfg not applied

2017-04-12 Thread Carlos Konstanski
i user with sudo, ssh-key, etc. > > m foster writes: > >> The only thing I can think of is that the default user should just be >> "default", not qualified with "name". Perhaps that is clobbering your next >> entry or just creating a syntax error. >>

Re: [Openstack-operators] [openstack-operators] [nova] cloud.cfg not applied

2017-04-12 Thread Carlos Konstanski
econd ckonstanski user with sudo, ssh-key, etc. m foster writes: > The only thing I can think of is that the default user should just be > "default", not qualified with "name". Perhaps that is clobbering your next > entry or just creating a syntax error. > > On Wed, Apr

[Openstack-operators] [openstack-operators] [nova] cloud.cfg not applied

2017-04-12 Thread Carlos Konstanski
leshoot this. What is the mechanism that gets the cloud.cfg applied? Any info would be helpful, even a link. Sincerely, Carlos Konstanski ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/m

Re: [Openstack-operators] Glance image 'visibility' migration in Ocata

2017-01-24 Thread Carlos Konstanski
- There seems to be no difference between public and community, and the README does not do an adequate job of explaining the difference. - There is nothing conceptually wrong with having something be private and letting it have a list of members. Private does not have to mean "just one user"