Re: [Openstack-operators] Openstack Version discovery with the cli client.

2018-08-07 Thread George Mihaiescu
Hi Saverio, I think only the API versions supported by some of the endpoint are discoverable, as described here: https://wiki.openstack.org/wiki/VersionDiscovery curl https://x.x.x.x:9292/image curl https://x.x.x.x:8774/compute Cheers, George On Tue, Aug 7, 2018 at 9:30 AM, Saverio Proto

Re: [Openstack-operators] [Openstack] Recovering from full outage

2018-07-06 Thread George Mihaiescu
ances. > > In summary; DHCP requests are being sent, but are never received. > > *Torin Woltjer* > > *Grand Dial Communications - A ZK Tech Inc. Company* > > *616.776.1066 ext. 2006* > * <http://www.granddial.com>www.granddial.com <http://www.granddial.com>* &g

Re: [Openstack-operators] [Openstack] Recovering from full outage

2018-07-05 Thread George Mihaiescu
m>www.granddial.com <http://www.granddial.com>* > > -- > *From*: George Mihaiescu > *Sent*: 7/5/18 10:38 AM > *To*: torin.wolt...@granddial.com > *Subject*: Re: [Openstack] Recovering from full outage > Did you restart the neutron-dhcp-agent and rebooted the VMs? > > On T

Re: [Openstack-operators] [Openstack] Recovering from full outage

2018-07-03 Thread George Mihaiescu
, however I cannot ping any > of the instances floating IPs or the neutron router. And when logging into an > instance with the console, there is no IP address on any interface. > > Torin Woltjer > > Grand Dial Communications - A ZK Tech Inc. Company > > 616.776.106

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-17 Thread George Mihaiescu
True" and "vif_plugging_timeout = 300" and run another large test, just to confirm. We usually run these large tests after a version upgrade to test the APIs under load. On Thu, May 17, 2018 at 11:42 AM, Matt Riedemann <mriede...@gmail.com> wrote: > On 5/17/2018 9:

Re: [Openstack-operators] attaching network cards to VMs taking a very long time

2018-05-17 Thread George Mihaiescu
We use "vif_plugging_is_fatal = False" and "vif_plugging_timeout = 0" as well as "no-ping" in the dnsmasq-neutron.conf, and large rally tests of 500 instances complete with no issues. These are some good blogposts about Neutron performance:

Re: [Openstack-operators] Guest crash and KVM unhandled rdmsr

2017-10-17 Thread George Mihaiescu
Hi Blair, We had a few cases of compute nodes hanging with the last log in syslog being related to "rdmsr", and requiring hard reboots: kvm [29216]: vcpu0 unhandled rdmsr: 0x345 The workloads are probably similar to yours (SGE workers doing genomics) with CPU mode host-passthrough, on top of

Re: [Openstack-operators] Experience with Cinder volumes as root disks?

2017-08-02 Thread George Mihaiescu
I totally agree with Jay, this is the best, cheapest and most scalable way to build a cloud environment with Openstack. We use local storage as the primary root disk source which lets us make good use of the slots available in each compute node (6), and coupled with the Raid10 gives good I/O

Re: [Openstack-operators] [scientific] Lightning talks on Scientific OpenStack

2017-04-28 Thread George Mihaiescu
r a lightning talk, and enables us to fit one more > in. > > Best wishes, > Stig > > > > On 27 Apr 2017, at 20:29, George Mihaiescu <lmihaie...@gmail.com> wrote: > > > > Hi Stig, it will be 10 minutes sessions like in Barcelona? > > > > Thanks,

Re: [Openstack-operators] [scientific] Lightning talks on Scientific OpenStack

2017-04-27 Thread George Mihaiescu
Hi Stig, it will be 10 minutes sessions like in Barcelona? Thanks, George > On Apr 26, 2017, at 03:31, Stig Telfer wrote: > > Hi All - > > We have planned a session of lightning talks at the Boston summit to discuss > topics specific for OpenStack and research

Re: [Openstack-operators] Mixed env for nova (ceph for some compute nodes, local disk for the rest): qcow2 or raw images ?

2017-04-05 Thread George Mihaiescu
Hi Massimo, You can upload the images twice, in both qcow2 and raw format, then create a host aggregate for your "local-disk" compute nodes and set its metadata to match the property you'll set on your qcow2 images. When somebody will start a qcow2 version of the image, it will be scheduled on

Re: [Openstack-operators] [BostonSummit] [Forum] seeking Boston Summit Forum group to discuss protected data cloud

2017-03-06 Thread George Mihaiescu
Hi Evan, I believe the scientific working group will have at least a meeting focused on this subject ( https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg) Contact me off-list if you want to chat about protected data, as I'm the architect for a fairly large environment that deals

Re: [Openstack-operators] Change 'swap' in a flavor template

2016-12-15 Thread George Mihaiescu
Can you not update the flavour in dashboard? > On Dec 15, 2016, at 09:34, William Josefsson > wrote: > >> On Thu, Dec 15, 2016 at 9:40 PM, Mikhail Medvedev >> wrote: >> >> I could not figure out how to set swap on existing flavor fast enough,

Re: [Openstack-operators] How to tune scheduling for "Insufficient compute resources" (race conditions ?)

2016-11-30 Thread George Mihaiescu
Try changing the following in nova.conf and restart the nova-scheduler: scheduler_host_subset_size = 10 scheduler_max_attempts = 10 Cheers, George On Wed, Nov 30, 2016 at 9:56 AM, Massimo Sgaravatto < massimo.sgarava...@gmail.com> wrote: > Hi all > > I have a problem with scheduling in our

Re: [Openstack-operators] Audit Logging - Interested? What's missing?

2016-11-17 Thread George Mihaiescu
Same need here, I want to know who changed a security group and what change was done. Just the logged POST on the API is not enough to properly audit the operation. > On Nov 16, 2016, at 19:51, Kris G. Lindgren wrote: > > I need to do a deeper dive on audit logging. >

Re: [Openstack-operators] ML2/OVS odd GRE brokenness

2016-11-08 Thread George Mihaiescu
Hi Jonathan, The openvswitch-agent is out of sync on compute 4, try restarting it. > On Nov 8, 2016, at 17:43, Jonathan Proulx wrote: > > > I have an odd issue that seems to just be affecting one private > network for one tenant, though I saw a similar thing on a

Re: [Openstack-operators] Disable console for an instance

2016-10-27 Thread George Mihaiescu
the console. You could create a special role that has console access and change the policy file to reference that role for the "compute:get_vnc_console", for example. I don't think you can do it on per-flavor basis. Cheers, George On Thu, Oct 27, 2016 at 10:24 AM, Blair Bethwaite <blair.bethwa.

Re: [Openstack-operators] Disable console for an instance

2016-10-27 Thread George Mihaiescu
Hi Blair, Did you try playing with Nova's policy file and limit the scope for "compute_extension:console_output": "" ? Cheers, George On Thu, Oct 27, 2016 at 10:08 AM, Blair Bethwaite wrote: > On 27 October 2016 at 16:02, Jonathan D. Proulx