On Mon, 05 Jan 2015 11:10:41 -0500
Jay Pipes wrote:
> >
> > Thoughts on getting consistency across all 3 projects (and possibly
> > others)?
>
> Yeah, I personally like the second option as well, but agree that
> consistency is the key (pun intended) here.
>
> I would say let's make a decision
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim wrote:
> On 01/27/2015 06:31 PM, Doug Hellmann wrote:
>
>> On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
>>
>>> I'd like to build tool that would be able to profile messaging over
>>> various deployments. This "tool" would give me an ability
+1
Regards,
Sergey.
On 28 January 2015 at 10:52, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com> wrote:
> +1
>
> Pavlo Shchelokovskyy
> Software Engineer
> Mirantis Inc
> www.mirantis.com
>
> On Wed, Jan 28, 2015 at 8:26 AM, Thomas Herve
> wrote:
>
>>
>> > Hi all
>> >
>> > After having a l
On Tue, 06 Jan 2015 07:31:19 -0500
Jay Pipes wrote:
> On 01/06/2015 06:25 AM, Chen CH Ji wrote:
> > Based on nova-specs api-microversions.rst
> > we support following function definition format, but it violate the
> > hacking rule pep8 F811 because duplicate function definition
> > we should use
Hi,
*But with introduction of plugins and granular deployment, in my opinion,
we need to be able*
*to specify that task should run specifically on primary, or on
secondaries. Alternative to this approach would be - always run task on all
controllers, and let task itself to verify that it is execu
Hi,
Approximately a year and a half ago, the default DHCP lease time in Neutron
was increased from 120 seconds to 86400 seconds.[1] This was done with the
goal of reducing DHCP traffic with very little discussion (based on what I
can see in the review and bug report). While it it does indeed reduc
On 25/01/2015 11:00 PM, Ian Wells wrote:
Lots of open questions in here, because I think we need a long conversation
on the subject.
On 23 January 2015 at 15:51, Kevin Benton wrote:
It seems like a change to using internal RPC interfaces would be pretty
unstable at this point.
Can we start b
Miguel Ángel Ajo
On Wednesday, 28 de January de 2015 at 09:50, Kevin Benton wrote:
> Hi,
>
> Approximately a year and a half ago, the default DHCP lease time in Neutron
> was increased from 120 seconds to 86400 seconds.[1] This was done with the
> goal of reducing DHCP traffic with very litt
Hi All!
Thanks for the feedback!
I'll remove xattr from the requirements in my change set.
Currently i'm working on a workaround to execute 'getfattr' instead of the
xattr api call. We can asure getfattr is available via package dependencies
of our client who has to be installed either way.
I'm a
But without this separation on orchestration layer, we are unable to
differentiate between nodes.
What i mean is - we need to run subset of tasks on primary first and then
on all others, and we are using role as mapper
to node identities (and this mechanism was hardcoded in nailgun for a long
time)
Monty Taylor wrote:
> You'll notice that I did say in my suggestion that ANYONE should be able
> to propose a name - I believe that would include non-dev people. Since
> the people in question are marketing people, I would imagine that if any
> of them feel strongly about a name, that it should be
On 28/01/15 10:23 +0200, Denis Makogon wrote:
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim wrote:
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
I'd like to build tool that would be able to profile messaging
On Wed, Jan 28, 2015 at 11:36:41AM +1000, Angus Salkeld wrote:
>Hi all
>
>After having a look at the stats:
>http://stackalytics.com/report/contribution/heat-group/90
>http://stackalytics.com/?module=heat-group&metric=person-day
>
>I'd like to propose the following changes to
On 27/01/15 13:22 -0500, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:44 PM, Julien Danjou wrote:
On Tue, Jan 27 2015, Clark Boylan wrote:
> So the issue is that the garbage collector segfaults on null objects in
> the to be garbage collected list. Which means that by the time garbage
> c
Nik,
> I'm now here and I don't agree that we need to remove "changes"
> attribute. On the opposite, I think this is the only attribute which
> should be looked at on UI and backend, and all these
> "pending_addition" and "pending_someotherstuff" are obsolete and
> needless.
You're absolutely rig
On Fri, 23 Jan 2015 15:51:54 +0200
Andrey Kurilin wrote:
> Hi everyone!
> After removing nova V3 API from novaclient[1], implementation of v1.1
> client is used for v1.1, v2 and v3 [2].
> Since we moving to micro versions, I wonder, do we need such
> mechanism of choosing api version(os-compute-a
On Fri, 23 Jan 2015 16:53:55 +
"Day, Phil" wrote:
> Hi Folks,
>
> Is there any support yet in novaclient for requesting a specific
> microversion ? (looking at the final leg of extending
> clean-shutdown to the API, and wondering how to test this in devstack
> via the novaclient)
>
No, s
Hi,
we definitely need such separation on orchestration layer.
> Is it possible to have significantly different sets of tasks for
controller and primary-controller?
Right now we already do different things on primary and secondary
controllers, but it's all conducted in the same manifest and cont
Adam Lawson writes:
Hi Adam,
> I'm researching for a web-based visualization that simply displays
> OpenStack Swift and/or node status, cluster health etc in some manner.
I wrote Swift Browser, which will let you browse the containers and
objects in your Swift cluster:
Repository: https://gi
+1 on all changes.
Regards,
Thomas
> From: Angus Salkeld
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 28/01/2015 02:40
> Subject: [openstack-dev] [Heat] core team changes
>
> Hi all
> After having a look at the stats:
> http://stackalytics.com/report/contribut
Hi Vladimir,
It's not clear what problem you are going to solve with putting serializers
alongside with deployment scripts/tasks.
For sure there is no way for this serializers to have access to the
database,
because with each release there will be a huge probability to get this
serializers broken
Igor,
But why can't we implement it properly on the first try? It doesn't
seem like a hard task and won't take much time.
On Wed, Jan 28, 2015 at 12:50 PM, Igor Kalnitsky
wrote:
> Nik,
>
>> I'm now here and I don't agree that we need to remove "changes"
>> attribute. On the opposite, I think thi
Hello,
I want to use L3 functionalities with own device in place of normal
L3agent. So I think that best way will be to write own L3 service plugin
which will configure my router on my special device. But I don't know
now few things. For example if I'm creating new port in router
(router-inte
Hi,
+1 for having primary-controller role in terms of deployment.
In our tasks user should be able to run specific task on primary-controller.
But I agree that it can be tricky because after the cluster is deployed, we
cannot say who is really primary, is there a case when it's important to
know
w
Thanks for your response.
We have analysed the issue further and the DG is not the problem.
We have taken tcpdumps on all interfaces and we can see that the ping reaches
the VIP on the driver virtual appliance and the virtual appliance responds to
the ping. It responds with the mac address o
+1 to replace simple to HA with one controller
/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/m
On Wed, Jan 28, 2015 at 11:39 AM, Flavio Percoco wrote:
> On 28/01/15 10:23 +0200, Denis Makogon wrote:
>
>>
>>
>> On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim wrote:
>>
>>On 01/27/2015 06:31 PM, Doug Hellmann wrote:
>> On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
>>
>
>
> It's not clear what problem you are going to solve with putting serializers
> alongside with deployment scripts/tasks.
>
I see two possible uses for specific serializer for tasks:
1. Compute additional information for deployment based not only on what is
present in astute.yaml
2. Request info
Hello Vishvananda,
> Initialize connection passes that data to cinder in the call. The connector
> dictionary in the call should contain the info from nova:
>
> https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L1051
Ah yes, I see.
Thank you very much!
Regards,
Phil
--
On 01/27/2015 10:35 PM, James E. Blair wrote:
> Lauren Sell writes:
>
>> Hey Monty,
>>
>> I’d like to weigh in here, because I think there have been some
>> misunderstandings around Lemming-gate. I’m glad you raised your
>> concerns; it’s a good test of release naming for us all to discuss and
>>
Take up on this was a bit lower then I would have hoped but lets go
ahead with it anyways ;-)
we had 6 volunteers altogether.
I've taken the list of current tripleo bugs and split them into groups
of 15 (randomly shuffled) and assigned a group to each volunteer.
Each person should take a look at
Hi,
At the mid cycle meet up it was discussed that we need to prioritize the BP's
that require review. This will at least get us a chance of getting something
into Nova this cycle.
The following BP's are ready for review:
1. Ephemeral disk support -
https://blueprints.launchpad.net/nova/+spe
Hi everyone,
When we first introduced the cross-project specs (specs for things that
may potentially affect all OpenStack projects, or where more convergence
is desirable), we defaulted to rather simple rules for approval:
- discuss the spec in a cross-project meeting
- let everyone +1/-1 and see
Putting the right tag in the subject to see if somone can help answer the
below
thanx,
deepak
On Tue, Jan 27, 2015 at 7:57 PM, Bharat Kumar
wrote:
> Hi,
>
> I have seen Sean Dague's patch [1], if I understood correctly, by this
> patch we can reduce the number of DEVSTACK_GATE variables that
Quick top-post apology...
It's entirely possible that there are people who are reading these lists
who do not personally know me or my tendency to overuse hyperbole.
I would like to formally apologize for both the subject of this thread
and my use of the word autocratic. They are both inflammator
On 01/28/2015 09:50 AM, Kevin Benton wrote:
Hi,
Approximately a year and a half ago, the default DHCP lease time in
Neutron was increased from 120 seconds to 86400 seconds.[1] This was
done with the goal of reducing DHCP traffic with very little
discussion (based on what I can see in the revi
I can try to comment on your questions... inline @PCM
PCM (Paul Michali)
IRC pc_m (irc.freenode.com)
Twitter... @pmichali
On Tue, Jan 27, 2015 at 9:45 PM, shihanzhang wrote:
> Hi Stacker:
>
> I am a novice, I want use Neutron VPNaas, through my preliminary
> understandin
Oleg,
In 6.0 we build OS target images during Fuel ISO building and then we just
put them on the ISO. In 6.1 we are planning to build them (at least Ubuntu
one) on the master node. We deliberately don't use DIB because it is all
about cloud case. DIB downloads pre-built cloud images (ubuntu, rhel,
+1
On Tue, Jan 27 2015, Angus Salkeld wrote:
> Hi all
>
> After having a look at the stats:
> http://stackalytics.com/report/contribution/heat-group/90
> http://stackalytics.com/?module=heat-group&metric=person-day
>
> I'd like to propose the following changes to the Heat core team:
>
> Add:
> Qi
On Wed, Jan 28, 2015, at 03:23 AM, Denis Makogon wrote:
> On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim wrote:
>
> > On 01/27/2015 06:31 PM, Doug Hellmann wrote:
> >
> >> On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
> >>
> >>> I'd like to build tool that would be able to profile messa
Nik,
I'm sure it requires at least a spec, since there are things that
should be discussed. Who can do it in this release cycle? If there's a
person I'm +1 for refactoring; otherwise - I'd prefer to remove it to
make code more clear.
Thanks,
Igor
On Wed, Jan 28, 2015 at 12:44 PM, Nikolay Markov
Vishvananda Ishaya wrote on 01/27/2015 04:29:50 PM:
> From: Vishvananda Ishaya
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 01/27/2015 04:32 PM
> Subject: Re: [openstack-dev] [nova] [api] Get servers with limit and
> IP address filter
>
> The network info for a
On 2015-01-28 02:42:28 + (+), Douglas Mendizabal wrote:
> Thanks for the heads up, and for adding the stable-compat-jobs to
> the client. [1] This is an interesting problem, since the
> proposal bot keeps the python-barbicanclient requirements in sync
> with global-requirements. I’m not s
On 27/01/15 20:36, Angus Salkeld wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-group&metric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Qiming Teng
Huang Tianhu
On 2015-01-28 10:29:38 +0100 (+0100), Thierry Carrez wrote:
> The proposal as it stands (https://review.openstack.org/#/c/150604/4)
> currently excludes all non-ATCs from voting, though. The wider
> "community" was included in previous iterations of the naming process,
> so this very much feels lik
On 28/01/15 23:27, Jeremy Stanley wrote:
> On 2015-01-28 10:29:38 +0100 (+0100), Thierry Carrez wrote:
>> The proposal as it stands (https://review.openstack.org/#/c/150604/4)
>> currently excludes all non-ATCs from voting, though. The wider
>> "community" was included in previous iterations of the
Intel folks,
Belated welcome to Sahara! Thank you for your recent commits.
Moving this thread to openstack-dev so others may contribute, cc'ing
Daniele and Pietro who pioneered the Spark plugin.
I'll respond with another email about Oozie work, but I want to
address the Spark/Swift issue in CDH
Hello,
I am trying to understand how a nova component can be run parallely on a
host. From the developer reference documentation it seems to indicate that
all the openstack services use green thread model of threading. Is it the
only model of parallelism for all the components or multiple processe
Hi folks,
I want to discuss the way we are working with generated keys for
nova/ceph/mongo and something else.
Right now we are generating keys on master itself, and then distributing
them by mcollective
transport to all nodes. As you may know we are in the process of making
this process describe
Hi folks,
We'll be having the Sahara team meeting in #openstack-meeting-3 channel.
Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20150129T14
--
Sincerely yours,
Sergey Lukjanov
Sahara Tech
Is there a way to overwrite the rule in our hacking (not familiar with
it ...)?
if so ,maybe we can do as suggested to avoid 811 for the class which has
Microversion definition? Thanks
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet:
Thierry Carrez writes:
> Monty Taylor wrote:
>> You'll notice that I did say in my suggestion that ANYONE should be able
>> to propose a name - I believe that would include non-dev people. Since
>> the people in question are marketing people, I would imagine that if any
>> of them feel strongly a
On 01/27/2015 10:51 AM, Doug Hellmann wrote:
> The infra team has been working hard to update our Python 3 testing for all
> projects to run on 3.4 instead of 3.3. Two of the last projects to be able to
> shift are oslo.messaging and oslo.rootwrap. The test suites for both projects
> trigger a s
> -Original Message-
> From: Tom Fifield [mailto:t...@openstack.org]
> Sent: 28 January 2015 16:37
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tc] Take back the naming process
>
> On 28/01/15 23:27, Jeremy Stanley wrote:
> > On 2015-01-28 10:29:38 +0100 (+0100),
Hi.
I'm vote for second option, cause if we will want to implement some unified
hierarchy (like Fuel as CA for keys on controllers for different env's)
then it will fit better than other options. If we implement 3rd option then
we will reinvent the wheel with SSL in future. Bare rsync as storage fo
3rd option is about using rsyncd that we run under xinetd on primary
controller. And yes, the main concern here is security.
On Wed, Jan 28, 2015 at 6:04 PM, Stanislaw Bogatkin
wrote:
> Hi.
> I'm vote for second option, cause if we will want to implement some
> unified hierarchy (like Fuel as CA
- Original Message -
> From: "Steve Gordon"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, 27 January, 2015 9:46:44 AM
> Subject: Re: [openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning and
> large pages
>
> - Original Message -
On 01/28/2015 01:29 AM, Thierry Carrez wrote:
> Monty Taylor wrote:
>> You'll notice that I did say in my suggestion that ANYONE should be able
>> to propose a name - I believe that would include non-dev people. Since
>> the people in question are marketing people, I would imagine that if any
>> of
I am of the opinion that the +1/-1 from non tc members can be valuable, but
similarly it would be easy to get just comments. The TC is the body I
expect to help determine the direction of cross project initiatives such as
the logging guidelines. As a PTL I feel confident the TC is the right body
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
If the problem is too many round trips our the interaction being too chatty
This is a good point: is the main issue that we feel the interaction is too
chatty, or that it’s too slow? I seem to hear people gravitating toward one or
the other when
Hello everyone,
there is already some code in our repository:
https://github.com/bigfootproject/savanna-image-elements
I did the necessary changes to have the Spark element use the cdh5
element. I updated also to Spark 1.2. The old cloudera HDFS-only
element is still needed for generating cdh4 im
On Jan 18, 2015, at 9:25 PM, Jay Pipes wrote:
> On 01/13/2015 07:41 AM, Sean Dague wrote:
>> On 01/09/2015 04:17 PM, Everett Toews wrote:
>>> One thing that has come up in the past couple of API WG meetings
>>> [1] is just how useful a proper API definition would be for the
>>> OpenStack projects
Folks,
one of the things we should not forget about - is out Fuel CI gating
jobs/tests. [1], [2].
One of them is actually runs simple mode. Unfortunately, I don't see
details about tests ran for [1], [2], but I'm pretty sure it's same set as
[3], [4].
I suggest to change tests. First of all, we n
The patch Kevin points out increased the lease to 24 hours (which I agree
is as arbitrary as 2 minutes, 8 minutes, or 1 century) because it
introduced use of DHCPRELEASE message in the agent, which is supported by
dnsmasq (to the best of my knowledge) and is functionally similar to
FORCERENEW.
Thi
Hi Dmitry!
1. as I mentioned above, we should have an interface, and if interface
doesn't
provide required information, you will have to fix it in two places,
in Nailgun and in external-serializers, instead of a single place i.e.
in Nailgun,
another thing if astute.yaml is a bad interf
I just want to toss in a quick 2 cents on the topic. It is important for
everyone to feel involved in the naming of our releases. It is part of who we
are. No one (including marketing) should be excluded from the discussion. I see
a lot of good feedback here and it should be fun again! Making it
Daniele,
Excellent! I'll have to keep a closer eye on bigfoot activity :) I'll
pursue this.
Best,
Trevor
On Wed, 2015-01-28 at 17:40 +0100, Daniele Venzano wrote:
> Hello everyone,
>
> there is already some code in our repository:
> https://github.com/bigfootproject/savanna-image-elements
>
+1
On Jan 27, 2015, at 7:36 PM, Angus Salkeld
wrote:
> Hi all
>
> After having a look at the stats:
> http://stackalytics.com/report/contribution/heat-group/90
> http://stackalytics.com/?module=heat-group&metric=person-day
>
> I'd like to propose the following changes to the Heat core team:
>
Sorry for late reply and thanks for bring this out, I agree the create_db
flag will increase the complexity
so I might do some PoC and write a spec to do it next release
For this sentence, I don't fully understand, are you suggesting to every db
usage remove should be a
patch for a test class? tha
On Wed, Jan 28, 2015, murali reddy wrote:
> I am trying to understand how a nova component can be run parallely on a
> host. From the developer reference documentation it seems to indicate that
> all the openstack services use green thread model of threading. Is it the
> only model of parallelism
Hi Dmitry,
I'm not sure if we should user approach when task executor reads
some data from the file system, ideally Nailgun should push
all of the required data to Astute.
But it can be tricky to implement, so I vote for 2nd approach.
Thanks,
On Wed, Jan 28, 2015 at 7:08 PM, Aleksandr Didenko
w
On Wed, Jan 28, 2015 at 11:36:41AM +1000, Angus Salkeld wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-group&metric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Q
On 1/28/2015 10:59 AM, Chen CH Ji wrote:
Sorry for late reply and thanks for bring this out, I agree the
create_db flag will increase the complexity
so I might do some PoC and write a spec to do it next release
For this sentence, I don't fully understand, are you suggesting to every
db usage r
Thanks JE.
On hosts with multi-core processors, it does not seem optimal to run a
single service instance with just green thread. I understand that on
controller node, we can run one or more nova services but still it does not
seem to utilize multi-core processors.
Is it not a nova scaling concer
On Wed, Jan 28, 2015, murali reddy wrote:
> On hosts with multi-core processors, it does not seem optimal to run a
> single service instance with just green thread. I understand that on
> controller node, we can run one or more nova services but still it does not
> seem to utilize multi-core proce
ok, I understand the purpose and way to go now, thanks for the sharing
and I will refactory the patches I have ,thanks
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Buil
And today's:
https://plus.google.com/hangouts/_/gyadkf7bm7wfpsrshlfenb4hiqa
Michael
On Tue, Jan 27, 2015 at 9:06 AM, Michael Still wrote:
> Today's hangout:
>
> https://plus.google.com/hangouts/_/gwjbog3l3omtk2f4tt5s5v4hn4a
>
> Michael
>
> On Tue, Jan 27, 2015 at 9:11 AM, Michael Still wrote:
On 2015-01-28 23:37:18 +0800 (+0800), Tom Fifield wrote:
> If logistics are getting complicated, is it necessary to lock it
> down so much? I vaguely recall a launchpad poll in the past, which
> was effectively open to the public? Is voting on the shortlisted
> names something we should just open w
James E. Blair wrote:
> Considering that the process used to be
> a poll of the ~openstack group on launchpad, it seemed like a fairly
> straightforward mapping to ATCs. I wanted to find the easiest way to
> get the most people in the community likely to vote as possible without
> needing to gener
F811 is not part of our hacking lib - it's in flake8. As far as I know,
it's not possible to selectively disable that for particular files or
methods. And as mentioned earlier in the list and when I asked in
#openstack-dev the feeling was that we don't want to disable F811 globally
because it's a
On Jan 28, 2015, at 7:05 AM, Steven Kaufer wrote:
> Vishvananda Ishaya wrote on 01/27/2015 04:29:50 PM:
>
> > From: Vishvananda Ishaya
> > To: "OpenStack Development Mailing List (not for usage questions)"
> >
> > Date: 01/27/2015 04:32 PM
> > Subject: Re: [openstack-dev] [nova] [api] Get s
Monty Taylor wrote:
> What if, to reduce stress on you, we make this 100% mechanical:
>
> - Anyone can propose a name
> - Election officials verify that the name matches the criteria
> - * note: how do we approve additive exceptions without tons of effort
Devil is in the details, as reading some
On Wed, Jan 28, 2015 at 9:52 AM, Salvatore Orlando wrote:
> The patch Kevin points out increased the lease to 24 hours (which I agree is
> as arbitrary as 2 minutes, 8 minutes, or 1 century) because it introduced
> use of DHCPRELEASE message in the agent, which is supported by dnsmasq (to
> the be
Thierry Carrez wrote:
> James E. Blair wrote:
>> Considering that the process used to be
>> a poll of the ~openstack group on launchpad, it seemed like a fairly
>> straightforward mapping to ATCs. I wanted to find the easiest way to
>> get the most people in the community likely to vote as possibl
Hi,
I would appreciate if someone replies the email below. Thanks.
Best regards,
Hongbin
On Sun, Jan 25, 2015 at 12:03 AM, Hongbin Lu wrote:
> Hi Heat team,
>
> I am looking for a solution to bridge between OpenStack and EC2. According
> to documents, it seems that Heat has multicloud support
On Jan 28, 2015, at 9:36 AM, Carl Baldwin wrote:
> On Wed, Jan 28, 2015 at 9:52 AM, Salvatore Orlando
> wrote:
>> The patch Kevin points out increased the lease to 24 hours (which I agree is
>> as arbitrary as 2 minutes, 8 minutes, or 1 century) because it introduced
>> use of DHCPRELEASE mess
The Oslo team is pleased to announce the release of:
oslo.vmware 0.9.0: Oslo VMware library for OpenStack projects
The primary reason for this release is to move the code
out of the oslo namespace package as part of
https://blueprints.launchpad.net/oslo-incubator/+spec/drop-namespace-packages
Fo
tl;dr: I wanted to be able to see what OpenStack APIs might look like in
Swagger and starting experimenting with Swagger in projects for things like
stubbing services, API test coverage, and code generation. In order to do
that I created wadl2swagger [1]. I've published copies [2] of what the
conve
A couple of important topics came up as a result of attending the Cross Project
Meeting. I’ve added both to the agenda for the next meeting on Thursday
2015/01/29 at 16:00 UTC.
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
The first is the suggestion from ttx to consider using openstac
The Oslo team is pleased to announce the release of:
oslosphinx 2.4.0: OpenStack Sphinx Extensions and Theme
There are two new features to highlight in this release:
1. The theme enforcement is now flexible, allowing any existing
theme with a name starting with “openstack” to be used. This
On 01/28/2015 11:36 AM, Thierry Carrez wrote:
> Monty Taylor wrote:
>> What if, to reduce stress on you, we make this 100% mechanical:
>>
>> - Anyone can propose a name
>> - Election officials verify that the name matches the criteria
>> - * note: how do we approve additive exceptions without tons
I'm glad this is getting some attention; it creates a visible bug in
Horizon that hurts the UX. (I'm adding the horizon category to this.)
But it sounds like Option 1 would potentially return a huge number of
instances. There's nothing to stop the user from asking for all starting
with "9". The UI
change or disable F811 might be too huge, so add #noqa might be best way we
have now unless we change the code logic ..
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Bui
Excerpts from Angus Salkeld's message of 2015-01-27 17:36:41 -0800:
> Hi all
>
> After having a look at the stats:
> http://stackalytics.com/report/contribution/heat-group/90
> http://stackalytics.com/?module=heat-group&metric=person-day
>
> I'd like to propose the following changes to the Heat c
Vova,
Its great to see so much progress on this, however it appears that we
have started merging code prior to the spec landing [0] lets get it
sorted ASAP.
[0] https://review.openstack.org/#/c/113491/
On Mon, Jan 19, 2015 at 8:21 AM, Vladimir Kuklin wrote:
> Hi, Fuelers and Stackers
>
> I am g
This release is breaking the stable/juno jobs, so we're putting a cap on
the library version in juno.
https://review.openstack.org/#/c/150919/
On Wed, Jan 28, 2015, at 12:53 PM, Doug Hellmann wrote:
> The Oslo team is pleased to announce the release of:
>
> oslo.vmware 0.9.0: Oslo VMware library
On Tue, 2015-01-27 at 14:41 -0800, Michael Still wrote:
> I would like to nominate Melanie Witt for the python-novaclient-core
> team.
I +1 this…
--
Kevin L. Mitchell
Rackspace
__
OpenStack Development Mailing List (not fo
On 25/01/15 00:03, Hongbin Lu wrote:
Hi Heat team,
I am looking for a solution to bridge between OpenStack and EC2.
According to documents, it seems that Heat has multicloud support but
the remote cloud(s) must be OpenStack.
It actually doesn't, although it is planned. (We have multi-region
s
Hi Kevin,
On 01/28/2015 03:50 AM, Kevin Benton wrote:
> Hi,
>
> Approximately a year and a half ago, the default DHCP lease time in Neutron
> was
> increased from 120 seconds to 86400 seconds.[1] This was done with the goal of
> reducing DHCP traffic with very little discussion (based on what I
On Wed, 2015-01-28 at 22:48 +0530, murali reddy wrote:
> On hosts with multi-core processors, it does not seem optimal to run a
> single service instance with just green thread. I understand that on
> controller node, we can run one or more nova services but still it
> does not seem to utilize mult
1 - 100 of 157 matches
Mail list logo
