I rebased the https://review.openstack.org/#/c/72576/ no-op change.
- Original Message -
> From: "Alan Pevec"
> To: "openstack-stable-maint"
> Cc: "OpenStack Development Mailing List"
> Sent: Tuesday, February 18, 2014 7:52:23 PM
> Subject: Re: [openstack-dev] [Openstack-stable-maint
At Wed, 19 Feb 2014 20:23:04 +0400,
Eugene Nikanorov wrote:
>
> Hi Sam,
>
> My comments inline:
>
>
> On Wed, Feb 19, 2014 at 4:57 PM, Samuel Bercovici wrote:
>
> > Hi,
> >
> >
> >
> > I think we mix different aspects of operations. And try to solve a non
> > "problem".
> >
> Not really, Adva
If I didn't understand it wrong, as long as you have an active review for
your change, and some level of interest / approval, then you should
be ok to finish it during the last Icehouse cycle, but of course,
your code needs to be approved to become part of Icehouse.
Cheers,
Miguel Ángel.
- O
At Tue, 18 Feb 2014 18:47:37 -0800,
Stephen Balukoff wrote:
>
> [1 ]
> [1.1 ]
> Small correction to my option #4 (here as #4.1). Neutron port_id should be
> an attribute of the 'loadbalancer' object, not the 'cluster' object.
> (Though cluster should have a network_id attribute).
Hi Eugene and
2014-02-20 8:57 GMT+01:00 Miguel Angel Ajo Pelayo :
> I rebased the https://review.openstack.org/#/c/72576/ no-op change.
And it failed in check-tempest-dsvm-neutron-pg with bug 1254890 -
"Timed out waiting for thing ... to become ACTIVE"
while previous check on Feb 17 failed in
check-tempest-dsvm
On 19/02/14 18:29, Dougal Matthews wrote:
> The question for me, is what passwords will we have and when do we need
> them? Are any of the passwords required long term.
We will need whatever the Heat template needs to generate all the
configuration files. That includes passwords for all services t
> I notice that we have changed "from swiftclient import Connection,
> HTTPException" to "from swiftclient import Connection, RequestException"
> at 2014-02-14, I don't know is it relational.
>
> I have reported a bug for this:
> https://bugs.launchpad.net/swift/+bug/1281886
Bug is a duplicate of
On Thu, Feb 20 2014, Sergey Lukjanov wrote:
Hi Sergey,
[…]
> * install GNU getopt by using homebrew (brew install gnu-getopt) or
> macports (port install getopts);
I've been doing that since day one to have things work locally.
I'm pretty sure it'd be OK to use getopt in a portable way rather
On 02/19/2014 06:10 PM, Ladislav Smola wrote:
Hello,
I would like to have your opinion about how to deal with passwords in
Tuskar-API
The background is, that tuskarAPI is storing heat template parameters in
its database, it's a
preparation for more complex workflows, when we will need to store
Hi David,
I have been working on an OpenStack resources cleanup script that allows you to
wipe out all resources in a given project, I guess you could use / adapt it for
your own case. It is available on github there:
https://github.com/cloudwatt/ospurge
You can also install it with pip (pip i
On Thu, Feb 20, 2014 at 10:22 AM, Julien Danjou wrote:
> I'm pretty sure it'd be OK to use getopt in a portable way rather than
> specifically the GNU version, but I had no idea if it was acceptable. If
> everybody think it is, I can give it a try.
>
In which sort of system setup other than maco
On 02/20/2014 10:12 AM, Radomir Dopieralski wrote:
On 19/02/14 18:29, Dougal Matthews wrote:
The question for me, is what passwords will we have and when do we need
them? Are any of the passwords required long term.
We will need whatever the Heat template needs to generate all the
configuratio
On Thu, Feb 20 2014, Chmouel Boudjnah wrote:
> In which sort of system setup other than macosx/freebsd generate_sample.sh
> is not working?
Likely everywhere GNU tools are not standard. So that's every system
_except_ GNU/Linux ones I'd say. :)
--
Julien Danjou
-- Free Software hacker
-- http:/
Hi,
Does HEAT support provisioning windows cluster? If so, can I also use
user-data to do some post install work for windows instance? Is there any
example template for this?
Thanks,
Jay
___
OpenStack-dev mailing list
[email protected]
Just noticed that there is already a bp tracing this, but no milestone was
set for it and the bp has been there for one year.
https://blueprints.launchpad.net/heat/+spec/windows-instances
Do we have any plan to finish this? Many customers are using windows
cluster, it is really cool if we can sup
Hi all,
I'm ready to help with syncing of DB code. But we'll need reviewers
attention in both oslo-incubator in nova :)
Thanks,
Roman
On Thu, Feb 20, 2014 at 5:37 AM, Lance D Bragstad wrote:
> Shed a little bit of light on Matt's comment about Keystone removing
> oslo-incubator code and the iss
Dear all,
I am interested to the integration of SAML with keystone and I am analysing
the following blueprint and its implementation:
https://blueprints.launchpad.net/keystone/+spec/saml-id
https://review.openstack.org/#/c/71353/
Looking at the code there is something I cannot undertand. In th
Dolph Mathews wrote:
> I just noticed the subject of this email referred to the "first batch"
> of invitations -- are there going to be subsequent batches of invites?
> If so, who was not included in the first batch that will be in
> subsequent batches?
Yes, as usual subsequent batches will be sen
On 20/02/14 09:12, Radomir Dopieralski wrote:
If we do need to store passwords it becomes a somewhat thorny issue, how
does Tuskar know what a password is? If this is flagged up by the
UI/client then we are relying on the user to tell us which isn't wise.
All the template parameters that are pa
Hi Jay,
Windows support in Heat is being developed, but is not complete yet, afaik.
You may already use Cloudbase Init to do the post-deploy actions on windows
- check [1] for the details.
Meanwhile, running a windows cluster is a much more complicated task then
just deploying a number of windows
马煜 wrote:
> who know when to freezy icehouse version ?
>
> my bp on ml2 driver has been approved, code is under review,
> but I have some trouble to deploy third-party ci on which tempest test run.
Feature freeze is on March 4th [1], so featureful code shall be proposed
*and* merged by then. I s
Hi Forent,
thanks for the link. Our current implementation of for the cleanup is a bit
buggy. I will give your script a try.
Maybe we could use it an replace the existing module.
Regards
Marc
From: Florent Flament [[email protected]]
Sent
Hello All
I and Roman Podoliaka are familiar with the changes made to common db code,
so we are ready to help with syncing it to OS projects.
But we want to ask you for more activity in reviewing of these patches.
Thanks, Victor
On Thu, Feb 20, 2014 at 4:27 AM, Doug Hellmann
wrote:
>
>
>
> On
On 20/02/14 11:21, Dougal Matthews wrote:
> If we do store passwords however, I wonder if we are
> best to encrypt everything to be safe. The overhead shouldn't be that
> big and it may be better than special casing the "NoEcho" values.
I think that before we start encrypting everything, we need t
Matt Riedemann wrote:
> This is kind of an aside, but I'm kind of confused now about how the
> syncs work with things that fall under oslo.rootwrap or oslo.messaging,
> like this patch [2]. It doesn't completely match the o-i patch, i.e.
> it's not syncing over openstack/common/rootwrap/wrapper.py
On 20/02/14 10:36, Radomir Dopieralski wrote:
On 20/02/14 11:21, Dougal Matthews wrote:
If we do store passwords however, I wonder if we are
best to encrypt everything to be safe. The overhead shouldn't be that
big and it may be better than special casing the "NoEcho" values.
I think that befo
On 20/02/14 11:46, Dougal Matthews wrote:
> On 20/02/14 10:36, Radomir Dopieralski wrote:
>> On 20/02/14 11:21, Dougal Matthews wrote:
>>> If we do store passwords however, I wonder if we are
>>> best to encrypt everything to be safe. The overhead shouldn't be that
>>> big and it may be better than
+1
Regards,
Alexander Ignatov
On 20 Feb 2014, at 03:02, John Speidel wrote:
> +1
> Andrew would be a good addition.
>
> -John
>
>
>
>
> On Wed, Feb 19, 2014 at 5:40 PM, Sergey Lukjanov
> wrote:
> Hey folks,
>
> I'd like to nominate Andrew Lazarew (alazarev) for savanna-core.
>
> He
On 20/02/14 12:02, Radomir Dopieralski wrote:
> On 20/02/14 11:46, Dougal Matthews wrote:
>> On 20/02/14 10:36, Radomir Dopieralski wrote:
>>> On 20/02/14 11:21, Dougal Matthews wrote:
If we do store passwords however, I wonder if we are
best to encrypt everything to be safe. The overhead
Hi Iwamoto,
> I agree with Samuel here. I feel the logical model and other issues
> (implementation etc.) are mixed in the discussion.
>
A little bit. While ideally it's better to separate it, in my opinion we
need to have some 'fair bit' of implementation details
in API in order to reduce code
Hi.
While implementing CRUD operations for node profiles in Tuskar (which
are essentially Nova flavors renamed) I encountered editing of flavors
and I have some doubts about it.
Editing of nova flavors in Horizon is implemented as
deleting-then-creating with a _new_ flavor ID.
For us it essential
Thank you Alan and Pete, I will wait for devstack-gate core approve
patch https://review.openstack.org/#/c/74451/
2014-02-20 17:14, Alan Pevec :
I notice that we have changed "from swiftclient import Connection,
HTTPException" to "from swiftclient import Connection, RequestException"
at 2014-02
Dolph, thanks for the information you provided.
Now I have two question:
1. Will neutron handle this event notification in the future?
2. I also wish neutron could verify that tenant_id is existent.
thanks
于 2014-02-20 4:33, Dolph Mathews 写道:
There's an open bug [1] against nova & neutron to h
Thanks Alexander for the detail explanation, really very helpful!
What I meant for a windows cluster is actually a windows application, such
as a WebSphere cluster or a hadoop windows cluster.
Seems I can use Cloudbase Init to do the post-deploy actions on windows,
but I cannot do some scale up o
Hi,
> On 19/02/14 10:09 +0100, Julien Danjou wrote:
> >On Wed, Feb 19 2014, Angus Salkeld wrote:
> >
> >> 2) use tulip and give up python 2
> >
> >+ use trollius to have Python 2 support.
> >
> > https://pypi.python.org/pypi/trollius
>
> So I have been giving this a go.
FYI I'm the author of Tr
On 20.2.2014 12:18, Radomir Dopieralski wrote:
On 20/02/14 12:02, Radomir Dopieralski wrote:
Anybody who gets access to Tuskar-API gets the
passwords, whether we encrypt them or not. Anybody who doesn't have
access to Tuskar-API doesn't get the passwords, whether we encrypt
them or not.
Yeah,
On 20/02/14 10:12, Radomir Dopieralski wrote:
> On 19/02/14 18:29, Dougal Matthews wrote:
>> The question for me, is what passwords will we have and when do we need
>> them? Are any of the passwords required long term.
>
> We will need whatever the Heat template needs to generate all the
> configu
I agree that we shouldn't be rushing something that's not ready, but I
guess it raises kind of a meta issue.
When we started this journey this was because v2 has a ton of warts, is
completely wonky on the code internals, which leads to plenty of bugs.
v3 was both a surface clean up, but it was als
On 19/02/14 08:48, Clint Byrum wrote:
> Since picking up Heat and trying to think about how to express clusters
> of things, I've been troubled by how poorly the CFN language supports
> using lists. There has always been the Fn::Select function for
> dereferencing arrays and maps, and recently we a
On 02/19/2014 08:58 PM, Adam Young wrote:
>> Can you give more detail here? I can see arguments for both ways of
>> doing this but continuing to use ids for ownership is an easier
>> choice. Here is my thinking:
>>
>> 1. all of the projects use ids for ownership currently so it is a
>> smaller chan
On 20/02/14 14:10, Jiří Stránský wrote:
> On 20.2.2014 12:18, Radomir Dopieralski wrote:
>> On 20/02/14 12:02, Radomir Dopieralski wrote:
>>> Anybody who gets access to Tuskar-API gets the
>>> passwords, whether we encrypt them or not. Anybody who doesn't have
>>> access to Tuskar-API doesn't get t
On 20/02/14 14:10, Jiří Stránský wrote:
> On 20.2.2014 12:18, Radomir Dopieralski wrote:
>> Thinking about it some more, all the uses of the passwords come as a
>> result of an action initiated by the user either by tuskar-ui, or by
>> the tuskar command-line client. So maybe we could put the key
On 02/20/2014 06:40 AM, Dmitry Tantsur wrote:
Hi.
While implementing CRUD operations for node profiles in Tuskar (which
are essentially Nova flavors renamed) I encountered editing of flavors
and I have some doubts about it.
Editing of nova flavors in Horizon is implemented as
deleting-then-cr
On 2014年02月20日 10:44, Christopher Yeoh wrote:
On Wed, 19 Feb 2014 12:36:46 -0500
Russell Bryant wrote:
Greetings,
The v3 API effort has been going for a few release cycles now. As we
approach the Icehouse release, we are faced with the following
question: "Is it time to mark v3 stable?"
My
Just to throw this out there, is this something we need for Icehouse?
Yes, I fully acknowledge that it's an ugly security hole. But what's our
story for how stable/clean Tuskar will be for Icehouse? I don't believe
the intention is for people to use this in a production environment yet,
so it
I think we still are going to multiple flavors for I, e.g.:
https://review.openstack.org/#/c/74762/
On Thu, 2014-02-20 at 08:50 -0500, Jay Dobies wrote:
>
> On 02/20/2014 06:40 AM, Dmitry Tantsur wrote:
> > Hi.
> >
> > While implementing CRUD operations for node profiles in Tuskar (which
> > are e
On 2/19/2014 12:26 PM, Chris Behrens wrote:
+1. I'd like to leave it experimental as well. I think the task work is
important to the future of nova-api and I'd like to make sure we're not rushing
anything. We're going to need to live with old API versions for a long time, so
it's important t
Hello!
In Murano's dashboard we have around 20 parameters that should be changed
or added to DJANGO_SETTINGS_MODULE. Currently all these parameters are
embedded into openstack_dashboard.settings during install with sed and
tools alike (and removed during uninstall).
Recently more clean and elegan
Ok
My previous answer was actually about the Feature proposal freeze
which happened two days ago.
Cheers,
Miguel Ángel.
On 02/20/2014 11:27 AM, Thierry Carrez wrote:
马煜 wrote:
who know when to freezy icehouse version ?
my bp on ml2 driver has been approved, code is under review,
but I have s
Hi,
Neutron permits to set a gateway IP outside of the subnet cidr by default.
And, thanks to the garyk's patch [1], it's possible to change this default
behavior with config flag 'force_gateway_on_subnet'.
This flag was added to keep the backward compatibility for people who need
to set the gate
Multiple flavors, but a single flavor per role, correct?
Mainn
- Original Message -
> I think we still are going to multiple flavors for I, e.g.:
> https://review.openstack.org/#/c/74762/
> On Thu, 2014-02-20 at 08:50 -0500, Jay Dobies wrote:
> >
> > On 02/20/2014 06:40 AM, Dmitry Tantsu
On 2/20/2014 7:22 AM, Sean Dague wrote:
I agree that we shouldn't be rushing something that's not ready, but I
guess it raises kind of a meta issue.
When we started this journey this was because v2 has a ton of warts, is
completely wonky on the code internals, which leads to plenty of bugs.
v3
On 20/02/14 14:47, Radomir Dopieralski wrote:
> On 20/02/14 14:10, Jiří Stránský wrote:
>> On 20.2.2014 12:18, Radomir Dopieralski wrote:
>
>>> Thinking about it some more, all the uses of the passwords come as a
>>> result of an action initiated by the user either by tuskar-ui, or by
>>> the tusk
Looking back, perhaps we should remove that flag and only authorize the
admin user to be able to set the gateway IP outside of the subnet cidr (for
tricky network), like only admin user can create provider network. And
require classic users to set gatway IP inside the subnet cidr.
Édouard.
On Th
I’d like to welcome Oleg as member of the core Neutron team as he has received
more than enough +1s and no negative votes from the other cores.
mark
On Feb 10, 2014, at 6:28 PM, Mark McClain wrote:
> All-
>
> I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg
> has
This would break IPv6. The gateway address, according to RFC 4861[1] Section
4.2 regarding Router Advertisements: "Source Address MUST be the link-local
address assigned to the interface from which this message is sent". This means
that if you configure a subnet with a Globally Unique Address
On 20/02/14 15:00, Tomas Sedovic wrote:
> Are we even sure we need to store the passwords in the first place? All
> this encryption talk seems very premature to me.
How are you going to redeploy without them?
--
Radomir Dopieralski
___
OpenStack-dev m
Ha yes, I completely forget IPv6 case.
Sorry and forget that thread.
Édouard.
On Thu, Feb 20, 2014 at 3:34 PM, Veiga, Anthony <
[email protected]> wrote:
> This would break IPv6. The gateway address, according to RFC 4861[1]
> Section 4.2 regarding Router Advertisements: "Source
We will move to Python33 in the future. More and more OpenStack projects
including python-novaclient are Python33 compatible. Do we have plan to
make Nova python33 compatible ?
As I know, oslo.messaging will not support python33 in Icehouse,this is
just one dependency for Nova, that means we can't
Thanks Mark,
thanks everyone for voiting! I'm so happy to become a member of this really
great team!
Oleg
On Thu, Feb 20, 2014 at 6:29 PM, Mark McClain wrote:
> I'd like to welcome Oleg as member of the core Neutron team as he has
> received more than enough +1s and no negative votes from the
On Thu, 20 Feb 2014 08:22:57 -0500
Sean Dague wrote:
>
> We're also duplicating a lot of test and review energy in having 2 API
> stacks. Even before v3 has come out of experimental it's consumed a
> huge amount of review resource on both the Nova and Tempest sides to
> get it to it's current sta
On 20/02/14 15:41, Radomir Dopieralski wrote:
> On 20/02/14 15:00, Tomas Sedovic wrote:
>
>> Are we even sure we need to store the passwords in the first place? All
>> this encryption talk seems very premature to me.
>
> How are you going to redeploy without them?
>
What do you mean by redeploy
On 20/02/14 15:57, Tomas Sedovic wrote:
> On 20/02/14 15:41, Radomir Dopieralski wrote:
>> On 20/02/14 15:00, Tomas Sedovic wrote:
>>
>>> Are we even sure we need to store the passwords in the first place? All
>>> this encryption talk seems very premature to me.
>>
>> How are you going to redeploy
From cinder code, we know that volume delete operation could be classify into
three categories;
1. General delelte: delete volumes that are in the status of available, error,
error_restoring, error_extending.
2. Force delete: delete volumes that are in the status of extending, attaching,
deta
On 02/20/2014 09:55 AM, Christopher Yeoh wrote:
> On Thu, 20 Feb 2014 08:22:57 -0500
> Sean Dague wrote:
>>
>> We're also duplicating a lot of test and review energy in having 2 API
>> stacks. Even before v3 has come out of experimental it's consumed a
>> huge amount of review resource on both the
On 20/02/14 16:02, Radomir Dopieralski wrote:
> On 20/02/14 15:57, Tomas Sedovic wrote:
>> On 20/02/14 15:41, Radomir Dopieralski wrote:
>>> On 20/02/14 15:00, Tomas Sedovic wrote:
>>>
Are we even sure we need to store the passwords in the first place? All
this encryption talk seems very
On 02/20/2014 03:57 PM, Tomas Sedovic wrote:
On 20/02/14 15:41, Radomir Dopieralski wrote:
On 20/02/14 15:00, Tomas Sedovic wrote:
Are we even sure we need to store the passwords in the first place? All
this encryption talk seems very premature to me.
How are you going to redeploy without th
On 20 February 2014 14:55, Christopher Yeoh wrote:
> On Thu, 20 Feb 2014 08:22:57 -0500
> Sean Dague wrote:
>>
>> We're also duplicating a lot of test and review energy in having 2 API
>> stacks. Even before v3 has come out of experimental it's consumed a
>> huge amount of review resource on both
Yup, current implementation depends on GNU getopt.
Julien, cool, that means I'm not crazy :)
About using common getopt functionally - at least long args will be removed
to support non GNU getopt. Rewriting it on pure python will be more useful
IMO.
On Thu, Feb 20, 2014 at 1:45 PM, Julien Danjou
Hello community.
I'd like to discuss feature of Neutron LBaaS in Heat.
Currently Heat resources are not identical to Neutron's.
There are four resources here:
'OS::Neutron::HealthMonitor'
'OS::Neutron::Pool'
'OS::Neutron::PoolMember'
'OS::Neutron::LoadBalancer'
Acc
Really don't want to have to resolve conflicts again or battle through making
the test suite succeed... Please can someone merge this?
https://review.openstack.org/#/c/72751/
https://bugs.launchpad.net/git-review/+bug/1279016
Thanks!
Alexander Jones
Double Negative R&D
www.dneg.com
On Thu, 20 Feb 2014 15:24:22 +
John Garbutt wrote:
>
> > Also micro and extension versioning is not the magic bullet which
> > will get us out of trouble in the future. Especially with the core
> > changes. Because even though versioning allows us to make changes,
> > for similar reasons to n
sphinxcontrib-pecanwsme is an extension to Sphinx for documenting APIs
built with the Pecan web framework and WSME.
What's New?
===
- Remove the trailing slash from the end of the URLs, as it results in
misleading feature documentation, see Ceilometer bug #1202744.
_
Hi All,
I have a question regarding creating/deleting a tenant in openstack (using
horizon or CLI). Is there any notification mechanism in place so that an
application get informed of such an event?
If not, can it be done using plugin to send create/delete notification to
an application?
Appreci
Yes, see:
http://docs.openstack.org/developer/keystone/event_notifications.html
On Thu, Feb 20, 2014 at 10:54 AM, Nader Lahouti wrote:
> Hi All,
>
> I have a question regarding creating/deleting a tenant in openstack (using
> horizon or CLI). Is there any notification mechanism in place so tha
Hello all,
I'm working in the following BP:
https://blueprints.launchpad.net/climate/+spec/tenant-reservation-concept, in
which the idea is to have the possibility to create "special" tenants that have
a lease for all of its associated resources.
The BP is in discussing phase and we were having
On 02/20/2014 05:58 AM, om prakash pandey wrote:
I am not able to run Tempest API tests. The typical ERROR I am getting
is "Connection Timed Out".
When checking into the logs I found out that tempest is trying to
access the admin URL which is a private IP for our deployment. Now,
Tempest is d
On 2/19/2014 4:05 PM, Matt Riedemann wrote:
The os-hosts OS API extension [1] showed up before I was working on the
project and I see that only the VMware and XenAPI drivers implement it,
but was wondering why the libvirt driver doesn't - either no one wants
it, or there is some technical reaso
Hi Everyone;
Our first python-openstack meeting was awesome: and I really want to thank
everyone who came, and for Doug teaching me the meeting bot :)
Minutes:
http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-02-19-19.01.html
Minutes
(text):http:
I've contacted foundation and they are ready to verify 5 options, so, we'll
choose them on todays irc team meeting (starting right now).
On Wed, Feb 19, 2014 at 12:27 AM, Sergey Lukjanov wrote:
> The voting is ended, you can ding results here -
> http://civs.cs.cornell.edu/cgi-bin/results.pl?num
Hi Christian,
2014-02-20 18:10 GMT+01:00 Martinez, Christian :
> Hello all,
>
> I'm working in the following BP:
> https://blueprints.launchpad.net/climate/+spec/tenant-reservation-concept,
> in which the idea is to have the possibility to create "special" tenants
> that have a lease for all of
Hi Doug,
2014-02-20 17:37 GMT+01:00 Doug Hellmann :
> sphinxcontrib-pecanwsme is an extension to Sphinx for documenting APIs
> built with the Pecan web framework and WSME.
>
> What's New?
> ===
>
> - Remove the trailing slash from the end of the URLs, as it results in
> misleading featur
Thanks Dolph for link. The document shows the format of the message and doesn't
give any info on how to listen to the notification.
Is there any other document showing the detail on how to listen or get these
notifications ?
Regards,
Nader.
> On Feb 20, 2014, at 9:06 AM, Dolph Mathews wrote:
Hi All,
I discussion recently came up inside of nova about what it means
supported version for a dependency means. in libvirt we gate on the
minimal version that we support but for all python dependencies we
gate on the highest version that passes our requirements. While we all
agree that having
All,
Murano is the OpenStack Application Catalog service which has been
developing on stackforge almost 11 months. Murano has been presented on HK
summit on unconference track and now we would like to apply for incubation
during Juno release.
As the first step we would like to get feedback from T
Sylvain, as I understand in BP description, Christian is about not exactly
reserving tenants itself like we actually do with VMs/hosts - it's just
naming for that. I think he is about two moments:
1) mark some tenants as "needed to be reserved" - speaking about resources
assigned to it
2) reserve
Dina: Yes, I'm talking about that. Thanks for the clarification.
Sylvain, let me put the use case that we have:
As part of project/tenant creation we would like to mark the tenant in such a
way that climate will automatically create a lease for the resources. All
non-production tenants/projects
Today we have released Designate Icehouse-2. The high-level launchpad details
can be found at https://launchpad.net/designate/icehouse/icehouse-2, as well as
a link to the tar file. This release includes almost a dozen blueprints,
including one for Domain Import/Export, as well as numerous bug f
2014-02-20 19:32 GMT+01:00 Dina Belova :
> Sylvain, as I understand in BP description, Christian is about not exactly
> reserving tenants itself like we actually do with VMs/hosts - it's just
> naming for that. I think he is about two moments:
>
> 1) mark some tenants as "needed to be reserved" -
Congratulations Oleg!!!
No need for welcoming you to the team, you were already part of ;-)
Edgar
From: Oleg Bondarev
Reply-To: OpenStack List
Date: Thursday, February 20, 2014 6:43 AM
To: OpenStack List
Subject: Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core
Thanks Mark
I agree with Bauza that the main purpose of Climate is to reserve resources,
and in the case of keystone it should reserve tenant, users, domains, etc.
So, it could be possible that climate is not the module in which the tenant
“lease” information should be saved. As stated in the use case, the
Thanks everyone who have joined Savanna meeting.
Here are the logs from the meeting:
Minutes:
http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-20-18.03.html
Log:
http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-20-18.03.log.html
--
Sincerely yours,
Sergey
We've agreed to send top 5 options to foundation for review, more details -
http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-20-18.03.html
On Thu, Feb 20, 2014 at 10:02 PM, Sergey Lukjanov wrote:
> I've contacted foundation and they are ready to verify 5 options, so,
> we'll
On 02/20/2014 01:31 PM, Joe Gordon wrote:
> Hi All,
>
> I discussion recently came up inside of nova about what it means
> supported version for a dependency means. in libvirt we gate on the
> minimal version that we support but for all python dependencies we
> gate on the highest version that pa
Thomas,
I feel your frustration, however before complaining please do follow
the actual chain of events.
Patch [1]: I asked a question which I never received an answer to.
Patch [2]: I did put a -1, but I have nothing against this patch per
se. This was only been recently abandoned and my -1 lied
On Thu, 2014-02-20 at 00:53 +, Vilobh Meshram wrote:
> Hello OpenStack Dev,
>
> We wanted to have your input on how different companies/organizations,
> using Openstack, are monitoring IP availability as this can be useful
> to track the used IP’s and total number of IP’s.
I presume you are t
On 02/20/2014 09:43 AM, 郭小熙 wrote:
> We will move to Python33 in the future. More and more OpenStack projects
> including python-novaclient are Python33 compatible. Do we have plan to
> make Nova python33 compatible ?
>
> As I know, oslo.messaging will not support python33 in Icehouse,this is
> ju
Running this test in tempest requires an ami image triple to be on the
disk where tempest is running in order for the test to upload it. It
would be a lot easier if this test could use a simple image file
instead. That image file could even be obtained from the cloud being
tested while configur
Thanks David, +++
This is a strong dependency to devstack, and it would be nice if we could
lose it.
andrea
-Original Message-
From: David Kranz [mailto:[email protected]]
Sent: 20 February 2014 21:32
To: OpenStack Development Mailing List
Subject: [openstack-dev] [qa] Does scenario.te
On 02/20/2014 04:31 PM, David Kranz wrote:
> Running this test in tempest requires an ami image triple to be on the
> disk where tempest is running in order for the test to upload it. It
> would be a lot easier if this test could use a simple image file
> instead. That image file could even be obta
1 - 100 of 130 matches
Mail list logo
