Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

2017-04-04 Thread Jay Pipes
On 04/04/2017 02:48 PM, Tim Bell wrote: Some combination of spot/OPIE What is OPIE? and Blazar would seem doable as long as the resource provider reserves capacity appropriately (i.e. spot resources>>blazar committed along with no non-spot requests for the same aggregate). Is this feasible?

Re: [Openstack-operators] [Openstack] Slow internet speed - Instances with floating IP

2017-04-04 Thread Kevin Benton
I recommend filing an issue against that speedtest-cli script. I noticed the timer seems to be started before the DNS lookup occurs (before call to urlopen). This means any DNS issues impact the measurement of what is supposed to be network throughput. On Apr 4, 2017 13:19, "John Petrini" wrote:

Re: [Openstack-operators] [Openstack] Slow internet speed - Instances with floating IP

2017-04-04 Thread John Petrini
Hi All, Turns out this was a DNS issue. The speedtest-cli script does a lot of lookups and these lookups were hanging due to parallel A and requests resulting in the unexpected results. I added the following to /etc/resolv.conf and the issue seems to be resolved. options single-request-reope

[Openstack-operators] [telecom-nfv] Meeting #23 tomorrow!

2017-04-04 Thread Curtis
Hi All, We will have our biweekly meeting tomorrow. [1] Feel free to add to the agenda. The openstack summit will be upon us soon. Hope to see you then. :) Thanks, Curtis. [1]: http://eavesdrop.openstack.org/#OpenStack_Operators_Telco_and_NFV_Working_Group ___

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

2017-04-04 Thread Tim Bell
Some combination of spot/OPIE and Blazar would seem doable as long as the resource provider reserves capacity appropriately (i.e. spot resources>>blazar committed along with no non-spot requests for the same aggregate). Is this feasible? Tim On 04.04.17, 19:21, "Jay Pipes" wrote: On 04/0

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

2017-04-04 Thread Jay Pipes
On 04/03/2017 06:07 PM, Blair Bethwaite wrote: Hi Jay, On 4 April 2017 at 00:20, Jay Pipes wrote: However, implementing the above in any useful fashion requires that Blazar be placed *above* Nova and essentially that the cloud operator turns off access to Nova's POST /servers API call for reg

[Openstack-operators] [scientific][scientific-wg] Reminder: Scientific WG IRC meeting today at 2100 UTC

2017-04-04 Thread Stig Telfer
Greetings! We have a Scientific WG IRC meeting later today at 2100 UTC in channel #openstack-meeting. Everyone is welcome. The agenda for today[1] is All Things Boston: Summit, Forum and Cloud Congress. Such a short agenda for so much activity! Scientific WG meeting details are available her

[Openstack-operators] resuming operators meetups team IRC meetings 2017-4-11

2017-04-04 Thread Chris Morgan
Hello all, I'd like to suggest we pick these meetings up again next week at 15:00 UTC (1500 UTC ) This seemed ok to the few hanging around on IRC (#openstack-operators) today at that time. Team wiki http

Re: [Openstack-operators] [Openstack] Slow internet speed - Instances with floating IP

2017-04-04 Thread John Petrini
Hi Mohit, The tenant networks use an MTU of 8950. The floating network uses and MTU of 9000. neutron net-show 4305e3d5-b083-4f33-a2a0-1dfccf1238b6 +---+--+ | Field | Value| +---

Re: [Openstack-operators] Slow internet speed - Instances with floating IP

2017-04-04 Thread John Petrini
Adding the OpenStack list in hopes this might get some attention there. Thanks All, ___ John Petrini ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

2017-04-04 Thread Tomáš Vondra
Hi! Did someone mention automation changing the spot instance capacity? I did an article in 2013 that proposes exactly that. The model forecasts the workload curve of the majority traffic, which is presumed to be interactive, and the rest may be used for batch traffic. The forecast used is SARIM