Thank you Mark for writing this up! If you are interested in new interop
programs, please comment on https://review.openstack.org/#/c/472785/.
In addition, we will also be discussing this during our weekly meeting on
Wednesday, 11:00 AM CST/ 16:00 UTC in #openstack-meeting-3. If you cannot
join us
I am fine with #2, and I am also fine with calling it a bug. Since the
enabled/disabled state for the other services didn’t actually do anything.
___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy
On 6/13/17, 8:46 PM, "Dan
Are we allowed to cheat and say auto-disabling non-nova-compute services
on startup is a bug and just fix it that way for #2? :) Because (1) it
doesn't make sense, as far as we know, and (2) it forces the operator to
have to use the API to enable them later just to fix their nova
service-list
On 6/13/2017 8:17 PM, Dan Smith wrote:
So it seems our options are:
1. Allow PUT /os-services/{service_uuid} on any type of service, even if
doesn't make sense for non-nova-compute services.
2. Change the behavior of [1] to only disable new "nova-compute"
services.
Please, #2. Please.
Fantastic. Great work, Sir!
Chris
Sent from my iPhone
> On Jun 13, 2017, at 8:09 PM, Edgar Magana wrote:
>
> Folks,
>
> I have good news. The time has been finally confirmed to be from 10am to 6pm.
> We are good with the current Eventbrite. Let’s spread the word!
>
Hi Dan,
I went through all the links from the search but there is no complete solution.
There are examples ODL with mininet, then ODL with openstack but there is no
example of openstack with mininet.
Do you have any other solutions?
Sent from my Samsung Galaxy smartphone.
Original
So it seems our options are:
1. Allow PUT /os-services/{service_uuid} on any type of service, even if
doesn't make sense for non-nova-compute services.
2. Change the behavior of [1] to only disable new "nova-compute" services.
Please, #2. Please.
--Dan
On 6/13/2017 12:19 PM, Matt Riedemann wrote:
With this change in Pike:
https://review.openstack.org/#/c/442162/
The PUT /os-services/* APIs to enable/disable/force-down a service will
now only work with nova-compute services. If you're using those to try
and disable a non-compute service,
Folks,
I have good news. The time has been finally confirmed to be from 10am to 6pm.
We are good with the current Eventbrite. Let’s spread the word!
https://www.eventbrite.com/e/mexico-city-openstack-operators-meetup-tickets-34989052197
Edgar
On 6/13/17, 9:02 AM, "Edgar Magana"
On 13/06/17 01:17 PM, Ignazio Cassano wrote:
> Hi Gordon, I had no enough time for trying with devstack.
you gave up after a day?
how about paste your ceilometer.conf and gnocchi.conf. did you follow
the steps here?
Hello all -
We have an IRC meeting coming up on Tuesday at 2100 UTC in channel
#openstack-meeting - about 90 minutes time.
This week we have Dr Xiaoyi Lu and Prof DK Panda from Ohio State University to
talk about HiBD, their project for creating RDMA-enabled optimisations of
Hadoop, Spark
With this change in Pike:
https://review.openstack.org/#/c/442162/
The PUT /os-services/* APIs to enable/disable/force-down a service will
now only work with nova-compute services. If you're using those to try
and disable a non-compute service, like nova-scheduler or
nova-conductor, those
Hi Gordon, I had no enough time for trying with devstack.
Anycase I tried to create an environment file ceil-openrc with the same
credentials stored in ceilometer.conf under service_c redentials section.
Doing:
source ceil-openrc
openstack user list
It shows users correctly, so I think c
Please do. 11am does feel too late :|
I logged back into IRC too, saw you pinged me there. let me know if I can
help.
Chris
On Tue, Jun 13, 2017 at 12:02 PM, Edgar Magana
wrote:
> Folks,
>
> We have a problem. Today during the Ops IRC meeting, I mentioned that the
>
Key news from today's meeting:
The approved Eventbrite for Mexico City, August event is expected today
The event will be 10am-6pm both days, $20 ticket price
Current plan is to cater only lunch and snacks
Calls for sponsorship of individual line items (badges, signs, food) will
be issued soon
I patched this back in liberty.
What version of Openstack are you using ?
Saverio
2017-06-08 19:36 GMT+02:00 Grant Morley :
> Ignore that now all,
>
> Managed to fix it by restarting the l3-agent. Looks like it must have been
> cached in memory.
>
> Thanks,
>
> On
But how is the gateway device configured. Have you setup NAT or routing on
it so traffic can get back?
On Jun 13, 2017 4:07 AM, "xiaotie" wrote:
> screenshot has eth0 up, but without IP address on it.
> I use following command to configure network:
> ifconfig eth0 192.168.5.204
screenshot has eth0 up, but without IP address on it.
I use following command to configure network:
ifconfig eth0 192.168.5.204 netmask 255.255.255.0
route add default gw 192.168.5.1
在2017-06-13,Kevin Benton 写道:-原始邮件-
发件人: Kevin Benton
发送时间:
18 matches
Mail list logo