I saw a commit for Deploying from VMware vCenter template and found it's
abandoned.
https://review.openstack.org/#/c/34903
Anyone knows the plan to support the deployment from VMware vCenter
template?
Thanks!
Best Regards___
OpenStack-dev
Hello!
Guys, I have no opportunity to hold our IRC meeting today. I propose to
move it tomorrow, the same time.
Please let me know if you are OK with that.
Thank you!
Best regards,
Dina Belova
Software Engineer
Mirantis Inc.
___
OpenStack-dev
Le 16/12/2013 10:41, Dina Belova a écrit :
Hello!
Guys, I have no opportunity to hold our IRC meeting today. I propose
to move it tomorrow, the same time.
Please let me know if you are OK with that.
Thank you!
+2 to this.
No regular meetings planned on Tuesdays 1000UTC as per
+2 too
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2013/12/16 Sylvain Bauza sylvain.ba...@bull.net
Le 16/12/2013 10:41, Dina Belova a écrit :
Hello!
Guys, I have no opportunity to hold our IRC meeting today. I propose to
move it tomorrow, the
On 12/12/2013 02:14 PM, Flavio Percoco wrote:
I've a draft in my head of how the amqp 1.0 driver could be
implemented and how to map the current expectations of the messaging
layer to the new protocol.
I think a separate thread to discuss this mapping is worth it. There
are some critical areas
I've had to rebase this a couple of times since to keep ahead of RPC version
numbers - sitting there with a +1 from Jenkins at the moment:
https://review.openstack.org/#/c/35303/
Phil
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: 12 December 2013 14:38
ok
On Mon, Dec 16, 2013 at 2:14 PM, Nikolay Starodubtsev
nstarodubt...@mirantis.com wrote:
+2 too
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2013/12/16 Sylvain Bauza sylvain.ba...@bull.net
Le 16/12/2013 10:41, Dina Belova a écrit :
Hello!
Hello Sreedhar,
I am focusing only on the OVS agent at the moment.
Armando fixed a few issues recently with the DHCP agent; those issues were
triggering a perennial resync; with his fixes I reckon DHCP agent response
times should be better.
I reckon Maru is also working on architectural
Hi all.
When I try to fix a bug:https://bugs.launchpad.net/nova/+bug/1242961,
I get a trouble.
To reproduce the bug is very easy. Live migrate a vm in block_migration
mode,
and then delelte the vm immediately.
The reason of this bug is as follow:
1. Because live migrate costs more time, so the
Hi,all
The storage array used by cinder in my experiment is produced by Huawei. The
vendor releases its own multipath named Ultrapath with the SAN.
Could I use the Ultrapath instead of dm-multipath in openstack?
Best wishes,
Qi
Qi Xiaozhen
CLOUD OS PDU, IT
Hello Salvatore,
Thanks for the updates. All the changes which you talked is from the agent
side.
From my tests, with multiple L2 agents running and sending/requesting
messages at the same time from the single neutron rpc server process is not
able to handle
All the load fast enough and
Hi!
This is a reminder that we will have another community meeting today in IRC
(#openstack-meeting) at 16.00 UTC.
Here’s the agenda: https://wiki.openstack.org/wiki/Meetings/MistralAgenda
As usually, you’re welcome to join!
Renat Akhmerov
@ Mirantis Inc.
On 12/16/2013 08:52 AM, Stephen Gran wrote:
On 16/12/13 03:47, Thomas Goirand wrote:
Hi,
I've been working over the last 2 months to get Ironic, TripleO and
Tuskar ready for an upload in Debian. However, for tuskar-ui, I'm facing
the fact that there's a lack of documentation.
It was easy to
Multiple RPC servers is something we should definitely look at.
I don't see a show-stopper reason for which this would not work, although I
recall we found out a few caveats one should be aware of when doing
multiple RPC servers when reviewing the patch for multiple API server (I
wrote them in
On 12/13/2013 03:08 PM, Ladislav Smola wrote:
Horizoners,
As discussed in TripleO and Horizon meetings, we are proposing to move
Tuskar UI under the Horizon umbrella. Since we are building our UI
solution on top of Horizon, we think this is a good fit. It will allow
us to get feedback and
Isn’t just handling the exception instance_not_found enough? By this time
source would’ve been cleaned up. Destination VM resources will get cleaned up
by the periodic task since the VM is not associated with this host. Am I
missing something here?
From: 王宏 [mailto:w.wangho...@gmail.com]
On 12/13/2013 05:22 PM, James Slagle wrote:
On Fri, Dec 13, 2013 at 03:04:09PM +0100, Imre Farkas wrote:
One note to deploy: It's not done only by Heat and Nova. If we
expect a fully functional OpenStack installation as a result, we are
missing a few steps like creating users, initializing and
On 13/12/13 16:37 +0100, Flavio Percoco wrote:
On 13/12/13 15:53 +0100, Thierry Carrez wrote:
Hi everyone,
TL;DR:
Incubation is getting harder, why not ask efforts to apply for a new
program first to get the visibility they need to grow.
Long version:
Last cycle we introduced the concept of
Hi All,
I have submitted a new blueprint which addresses the a common pattern
in the docker world. A usual pattern in the docker world is to use
environment variables to configure a container.
docker run -e SQL_URL=postgres://user:password@/db my-app
The nova docker driver doesn't support to
Hello Salvatore,
I agree with you on we need both items to improve the scaling and performance
of neutron server.
I am not a developer so can't implement the changes myself. If somebody is
going to implement I am more than happy to do the tests.
Thanks Regards,
Sreedhar Nathani
From:
On 2013/16/12 14:03, Matthias Runge wrote:
On 12/13/2013 03:08 PM, Ladislav Smola wrote:
Horizoners,
As discussed in TripleO and Horizon meetings, we are proposing to move
Tuskar UI under the Horizon umbrella. Since we are building our UI
solution on top of Horizon, we think this is a good
Flavio Percoco wrote:
What I'm arguing here is:
1. Programs that are not part of OpenStack's release cycle shouldn't
be considered official nor they should have the rights that integrated
projects have.
2. I think requesting Programs to exist at the early stages of the
project is not
Hi,
At the moment the administrator is able to retrieve diagnostics for a running
VM. Currently the implementation is very loosely defined, that is, each driver
returns whatever they have to return. This is problematic in a number of
respects:
1. The tempest tests were written specifically
Hi Eugene,
as you have already noticed there's already some overlap with your work
and the current tests development.
We should find a productive way to coordinate the efforts.
Thanks for starting the refactoring, in my opinion it's needed.
cheers,
Rossella
On Sat, Dec 14, 2013 at 4:53 PM,
On 12/16/2013 09:27 AM, Daniel Kuffner wrote:
Hi All,
I have submitted a new blueprint which addresses the a common pattern
in the docker world. A usual pattern in the docker world is to use
environment variables to configure a container.
docker run -e SQL_URL=postgres://user:password@/db
Hi Russel,
I have something that is pushing it for to stay in nova (at least the
compute drivers). I should have a gerrit branch for people to review soon.
Regards
chuck
On Mon, Dec 16, 2013 at 10:07 AM, Russell Bryant rbry...@redhat.com wrote:
On 12/16/2013 09:27 AM, Daniel Kuffner wrote:
On 12/15/2013 05:12 PM, Robert Collins wrote:
That said, doing anything to the network RPC API seems premature until
the Neutron question is resolved.
This.
I've been pretty much ignoring this API since it has been frozen and
almost deprecated for a long time. My plan was to revisit the
On 12/16/2013 10:12 AM, Chuck Short wrote:
I have something that is pushing it for to stay in nova (at least the
compute drivers). I should have a gerrit branch for people to review soon.
OK. Do you have any design notes for whatever you're proposing? That
would probably be easier to review
Hi Russell,
You actually propose to extend the whole nova stack to support
environment variables. Would any other driver benefit from this API
extension?
Is that what you imagine?
nova --env SQL_URL=postgres://user:password --image
Regarding the discussion you mentioned. Are there any
Hi Chuck,
yes please, I'm eager to see what you have. :)
Daniel
On Mon, Dec 16, 2013 at 4:12 PM, Chuck Short chuck.sh...@canonical.com wrote:
Hi Russel,
I have something that is pushing it for to stay in nova (at least the
compute drivers). I should have a gerrit branch for people to review
On 12/16/2013 03:32 PM, Jaromir Coufal wrote:
On 2013/16/12 14:03, Matthias Runge wrote:
On 12/13/2013 03:08 PM, Ladislav Smola wrote:
Horizoners,
As discussed in TripleO and Horizon meetings, we are proposing to move
Tuskar UI under the Horizon umbrella. Since we are building our UI
solution
Hi,
We will hold our third Git Integration working group meeting on IRC in #solum
on Monday, December 16, 2013 1700 UTC / 0900 PST. Previous meeting notes are
here [4]
Agenda for today's meeting:
* Administrative:
* Topics:
* Discuss lang-pack-examples spec for
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
Hi,
At the moment the administrator is able to retrieve diagnostics for a running
VM. Currently the implementation is very loosely defined, that is, each
driver returns whatever they have to return. This is problematic in a number
That would be great, I have also a couple of change request waiting
for approval. Would be good to know if it has any relevance in the
future.
https://review.openstack.org/#/c/59824/
https://review.openstack.org/#/c/62182/
https://review.openstack.org/#/c/62183/
On 16 December 2013 15:25, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
Hi,
At the moment the administrator is able to retrieve diagnostics for a
running VM. Currently the implementation is very loosely defined, that is,
each
On 12/16/2013 10:18 AM, Daniel Kuffner wrote:
Hi Russell,
You actually propose to extend the whole nova stack to support
environment variables. Would any other driver benefit from this API
extension?
Is that what you imagine?
nova --env SQL_URL=postgres://user:password --image
Yes.
On Mon, Dec 16, 2013 at 04:18:52PM +0100, Daniel Kuffner wrote:
Hi Russell,
You actually propose to extend the whole nova stack to support
environment variables. Would any other driver benefit from this API
extension?
Is that what you imagine?
nova --env SQL_URL=postgres://user:password
On 12/16/2013 10:39 AM, Daniel P. Berrange wrote:
On Mon, Dec 16, 2013 at 04:18:52PM +0100, Daniel Kuffner wrote:
Hi Russell,
You actually propose to extend the whole nova stack to support
environment variables. Would any other driver benefit from this API
extension?
Is that what you
On 13/12/13 19:06 +1300, Robert Collins wrote:
On 13 December 2013 06:24, Will Foster wfos...@redhat.com wrote:
I just wanted to add a few thoughts:
Thank you!
For some comparative information here from the field I work
extensively on deployments of large OpenStack implementations,
most
On Mon, Dec 16, 2013 at 03:37:39PM +, John Garbutt wrote:
On 16 December 2013 15:25, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
I'd like to propose the following for the V3 API (we will not touch V2
in case operators have
On 12/16/13 5:25 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Dec 16, 2013 at 06:58:24AM -0800, Gary Kotton wrote:
Hi,
At the moment the administrator is able to retrieve diagnostics for a
running VM. Currently the implementation is very loosely defined, that
is, each driver
I would block it in the API or have the API cancelling the migration first.
I don't see a reason why to start an operation that is meant to fail, which
also has a complex chain of event, following it failure.
Regardless of the above, I think that the suggested exception handling is
needed in
+1. Sandy has been both helpful and insightful, plus he happens to have a good
handle on the many moving parts that make up this project. :-)
-Phil
-Original Message-
From: Lu, Lianhao [mailto:lianhao...@intel.com]
Sent: Sunday, December 15, 2013 5:29 PM
To: OpenStack Development
could we use Taskflow https://wiki.openstack.org/wiki/TaskFlow to manage
task state and resource for this kind of tasks in Nova? Cinder has been an
pilot to use Taskflow for volume backup tasks. anyone interested in this
suggestion or has done some research to improve the live migration
workflow?
On Fri, Dec 13, 2013 at 11:32:01AM -0800, Fox, Kevin M wrote:
I hadn't thought about that use case, but that does sound like it
would be a problem.
That, at least, is not much of a problem, because you can block access
to the metadata via a blackhole route or similar after you complete
your
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday December 17th, at 19:00 UTC in
#openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interested in
I've got a blueprint [1] scheduled for icehouse-3 to add DB2 support to
Nova. That's blocked by a patch working it's way through
sqlalchemy-migrate to add DB2 support [2] there.
I've held off pushing any nova patches up until the sqlalchemy-migrate
DB2 support is merged (which is also blocked
Ah, u might be able to do what u said. Try it out and see how far u can get :)
I would be interested to know how u plan on waiting for all existing operations
to finish. Maybe it's not so hard, not really sure...
Sent from my really tiny device...
On Dec 15, 2013, at 9:43 PM, iKhan
+1 on a migration to make uuid a non-nullable column. I advocated a few
patches back in Havana that make assumptions based on the UUID being
present and unique per instance. If it gets nulled the VMware drivers will
have have breakage and I have no idea how to avoid that reasonably without
the
On 12/16/2013 11:45 AM, Matt Riedemann wrote:
1. Add a migration to change instances.uuid to non-nullable. Besides the
obvious con of having yet another migration script, this seems the most
straight-forward. The instance object class already defines the uuid
field as non-nullable, so it's
Hello,
Thanks for joining us today in IRC, here are the links to meeting minutes and
logs:
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-16-16.00.html
Logs:
http://eavesdrop.openstack.org/meetings/mistral/2013/mistral.2013-12-16-16.00.log.html
Join us next
On 12/16/2013 10:37 AM, Gordon Sim wrote:
On 12/12/2013 02:14 PM, Flavio Percoco wrote:
I've a draft in my head of how the amqp 1.0 driver could be
implemented and how to map the current expectations of the messaging
layer to the new protocol.
I think a separate thread to discuss this mapping
The idea being discussed is using 169.254.169.254 for long term messaging
between a vm and some other process. For example, Trove - TroveVM.
I guess this thread is getting too long. The details are getting lost.
Thanks,
Kevin
From: Lars Kellogg-Stedman
The Marconi project team holds a weekly meeting in #openstack-meeting-alt on
Tuesdays, 1500
UTChttp://www.timeanddate.com/worldclock/fixedtime.html?hour=15min=0sec=0.
The next meeting is Tomorrow, Dec. 10. Everyone is welcome, but please take a
minute to review the wiki before attending for
IIRC someone who shows up at
https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Meetings is planning on
working on that again for Icehouse-3 but there's some new debate on the
best way to implement the desired effect. The goal of that change would be
to avoid streaming the disk image out of
On 12/16/2013 10:29 AM, Fox, Kevin M wrote:
Yeah, this is similar to what I am proposing. I think we just about have just
about everything we need already.
Thread started out discussing a slightly different use case then below. The use
case is processing events like:
User performs backup
On 12/16/2013 11:59 AM, Russell Bryant wrote:
On 12/16/2013 11:45 AM, Matt Riedemann wrote:
1. Add a migration to change instances.uuid to non-nullable. Besides the
obvious con of having yet another migration script, this seems the most
straight-forward. The instance object class already
Hi,
I have registered two blueprints, one in Nova and one in Neutron to make
it a VIF attribute that the libvirt driver in Nova will honor.
https://blueprints.launchpad.net/neutron/+spec/vif-attribute-for-hairpinning
https://blueprints.launchpad.net/nova/+spec/nova-hairpin-vif-attribute
--
On 12/16/2013 04:22 PM, Jiri Tomasek wrote:
Thanks for pointing this out, In Horizon you can easily decide which
dashboards to show, so the Infrastructure management Horizon instance
can have Project and Admin dashboards disabled.
I think there has been discussed that some panels of Admin
Hi,
Doodle shows that the most suitable time is 10AM PST on Tuesday.
Lets keep this time for Metadata Repository\Catalog meeting in
#openstack-glance IRC channel.
See you tomorrow!
Thanks
Georgy
On Fri, Dec 13, 2013 at 12:09 PM, Georgy Okrokvertskhov
gokrokvertsk...@mirantis.com wrote:
Hi,
On 12/13/2013 01:53 PM, Tzu-Mainn Chen wrote:
On 2013/13/12 11:20, Tzu-Mainn Chen wrote:
These look good! Quick question - can you explain the purpose of Node
Tags? Are they
an additional way to filter nodes through nova-scheduler (is that even
possible?), or
are they there solely for
I've run into a use case that doesn't currently seem to have a great solution:
Let's say my users want to use a top-of-stack OpenStack project such as Heat,
Trove, etc. that I don't currently support in my deployment. There's absolutely
no reason these services can't live happily in a VM
+1
There is also the use case where a new service is being introduced for everyone
eventually but you wish to start with a few friends. In the event of problems,
the effort to tidy up is much less. Documentation can be updated with the
production environment.
Tim
-Original Message-
Hi guys,
The first working version of the Complex filter expressions in API queries
blueprint [1] was pushed for review[2].
We implemented a new query REST resource in order to provide rich query
functionality for samples, alarms and alarm history. The future plans (in
separated blueprints)
On Mon, Dec 16, 2013 at 9:49 AM, Thierry Carrez thie...@openstack.orgwrote:
Flavio Percoco wrote:
What I'm arguing here is:
1. Programs that are not part of OpenStack's release cycle shouldn't
be considered official nor they should have the rights that integrated
projects have.
2.
Hi,
I have installed Openstack with heat using packstack. One thing I
noticed
is that the Orchestration Heat option is only available inside a project
view.
Is this by design ?
My use case it to create a project with images, networks,routers and
firewall rules
in a single workflow. I looked
Thanks for support,
as a starting point we have chosen Ironic - we really want to see it as a
replacement of Fuel's existing provisioning layer, with an intention of
participation and delivery of many features which we already know from the
real-world installations with Fuel.
We are trying to be
eg use a 'env_' prefix for glance image attributes
We've got a couple of cases now where we want to overrides these
same things on a per-instance basis. Kernel command line args
is one other example. Other hardware overrides like disk/net device
types are another possibility
Rather than
On 17 December 2013 09:59, Mike Scherbakov mscherba...@mirantis.com wrote:
Thanks for support,
as a starting point we have chosen Ironic - we really want to see it as a
replacement of Fuel's existing provisioning layer, with an intention of
participation and delivery of many features which we
On 16/12/13 15:57, Sayaji Patil wrote:
Hi,
I have installed Openstack with heat using packstack. One thing I
noticed
is that the Orchestration Heat option is only available inside a
project view.
Is this by design ?
My use case it to create a project with images, networks,routers and
Sorry for lost subject in last message.
Is there a document that describes the api changes from v1 to v2,
similar to the one documenting nova v2 to v3?
-David
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 12/16/2013 04:17 PM, Georgy Okrokvertskhov wrote:
By they way, there is an initiative to create generic metadata
repository based on Glance project. As services endpoints are just URLs
they also can be stored in this Glance metadata repository and have all
features related to visibility and
So it's great to see a submission of savanna tests for tempest. We would
like to see these tests run before reviewing them. Is the intent that
savanna will be enabled by default in devstack? If not, then I guess
there will need to be separate savanna jobs. I see that right now there
are
Hi Neutron developers,
I submitted the following blue print.
https://blueprints.launchpad.net/neutron/+spec/enable-to-set-dhcp-port-attributes
It is a proposal to be enable to control dhcp port attributes
(especially ip address) by a user.
This is based on a real requirement from our customer.
On 12/16/2013 05:50 PM, Doug Hellmann wrote:
It might be good, to start out, if we all look at them. That way we
can all learn a bit about tempest, too. If you add ceilometer-core
as a reviewer gerrit will expand the group name.
Doug
Thanks, Doug. That makes sense. The only reason I asked
On Dec 13, 2013, at 8:06 PM, Isaku Yamahata isaku.yamah...@gmail.com wrote:
On Fri, Dec 06, 2013 at 04:30:17PM +0900,
Maru Newby ma...@redhat.com wrote:
On Dec 5, 2013, at 5:21 PM, Isaku Yamahata isaku.yamah...@gmail.com wrote:
On Wed, Dec 04, 2013 at 12:37:19PM +0900,
Maru Newby
Hi!
Actually, I have already filed cancel of LiveMigration with using taskflow
[0].
But my approach to blueprint was not so good at that time.
So, I rewrote this blueprint from also point of russelb.
I want to repush and wanted to approved.
If you have any suggestions, ideas etc...
I appreciate
On 12/16/2013 02:57 PM, Gabriel Hurley wrote:
I've run into a use case that doesn't currently seem to have a great solution:
Let's say my users want to use a top-of-stack OpenStack project such as Heat,
Trove, etc. that I don't currently support in my deployment. There's absolutely no reason
On 12/04/2013 12:35 PM, Henry Nash wrote:
On 4 Dec 2013, at 13:28, Dolph Mathews dolph.math...@gmail.com
mailto:dolph.math...@gmail.com wrote:
On Sun, Nov 24, 2013 at 9:39 PM, Adam Young ayo...@redhat.com
mailto:ayo...@redhat.com wrote:
The #1 pain point I hear from people in the
On 12/16/2013 08:39 PM, Adam Young wrote:
On 12/16/2013 02:57 PM, Gabriel Hurley wrote:
I've run into a use case that doesn't currently seem to have a great
solution:
Let's say my users want to use a top-of-stack OpenStack project such
as Heat, Trove, etc. that I don't currently support in my
On 12/16/2013 08:39 PM, Adam Young wrote:
snip
See the endpoint filtering blueprint from the Havana release as a
starting point. I think the difference between that and what you have
here is that these endpoints should only show up in a subset of the
service catalogs returned?
Hi All,
Prompted by a recent suggestion from Tom Fifield, I thought I'd gauge
some interest in either changing the weekly Cinder meeting time, or
proposing a second meeting to accomodate folks in other time-zones.
A large number of folks are already in time-zones that are not
friendly to our
04:00 or 05:00 UTC works for me.
On Tue, Dec 17, 2013 at 11:04 AM, John Griffith
john.griff...@solidfire.com wrote:
Hi All,
Prompted by a recent suggestion from Tom Fifield, I thought I'd gauge
some interest in either changing the weekly Cinder meeting time, or
proposing a second meeting to
Hi John,
I think the current meeting schedule, UTC 16:00, basically works for China
TZ (12AM), although it is not perfect. If we need to reschedule, I think
UTC 05:00 is better than UTC 04:00, since UTC 04:00 (China 12PM) is our
lunch time.
On Tue, Dec 17, 2013 at 11:04 AM, John Griffith
On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 chaoc...@gmail.com wrote:
Hi John,
I think the current meeting schedule, UTC 16:00, basically works for China
TZ (12AM), although it is not perfect. If we need to reschedule, I think UTC
05:00 is better than UTC 04:00, since UTC 04:00 (China 12PM) is our
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Instance groups
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hello John,
04:00 or 05:00 UTC works for me too.
On Tue, Dec 17, 2013 at 12:05 PM, John Griffith
john.griff...@solidfire.com wrote:
On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 chaoc...@gmail.com wrote:
Hi John,
I think the current meeting schedule, UTC 16:00, basically works for China
TZ (12AM),
Thanks Steve.
Regards,
Sayaji
On Mon, Dec 16, 2013 at 2:57 PM, Steve Baker sba...@redhat.com wrote:
On 12/17/2013 09:57 AM, Sayaji Patil wrote:
Hi,
I have installed Openstack with heat using packstack. One thing I
noticed
is that the Orchestration Heat option is only available
Added openstack-dev
On Mon, Dec 16, 2013 at 11:34:05PM +0100,
Erik Moe emoe...@gmail.com wrote:
Hi,
I have added a new document to the launchpad. Document should now be more
in line with what we discussed at the Icehouse summit.
Hi John,
Yes, alternating the time for each week should be fine. I just change my
gmail name to English... I think you can see my name now...
On Tue, Dec 17, 2013 at 12:05 PM, John Griffith john.griff...@solidfire.com
wrote:
On Mon, Dec 16, 2013 at 8:57 PM, 赵钦 chaoc...@gmail.com wrote:
Hi
Hi Mark, Ben
The reset() method in turn calls the *clear()* method which does an
*unregister_opt()*. However the unregister_opt only unregisters the
*config_opts*. The entire set of options inside *_opts* remain as is. We've
filed a bug https://bugs.launchpad.net/oslo/+bug/1261376 on the oslo
It seems that there's no document about the change from v1 to v2. Maybe the
change is very small. Only found some info in OpenStack release notes.
Cinder API v2
- List volumes/snapshots summary actually is a summary view. In v1 it
was the same as detail view.
- List volumes/snapshots
On Tue, 2013-12-17 at 11:17 +0530, Amala Basha Alungal wrote:
Hi Mark, Ben
The reset() method in turn calls the clear() method which does an
unregister_opt(). However the unregister_opt only unregisters the
config_opts. The entire set of options inside _opts remain as is.
We've filed a
I agree with Qin here that alternating might be a good option. I'm not
opposed to being present to both meetings though.
-Mike Perez
On Mon, Dec 16, 2013 at 9:31 PM, Qin Zhao chaoc...@gmail.com wrote:
Hi John,
Yes, alternating the time for each week should be fine. I just change my
gmail
So the grizzly API releases notes are dead on. (I put them together and
have worked with both API's ;) )
Unfortunately, a lot of the features in v2 got back ported to v1. The main
differences are in the upgrade notes.
-Mike Perez
On Mon, Dec 16, 2013 at 9:57 PM, Zhi Kun Liu
95 matches
Mail list logo
