Seems we have agreed on increasing minor version of UI markup to 2.1.
I've updated
https://blueprints.launchpad.net/murano/+spec/dynamic-ui-specify-no-explicit-name-field
On Thu, Jul 10, 2014 at 1:08 AM, Timur Sufiev wrote:
> Also agree with Stan.
>
> I'd like to refrain from bumping version to
On Thu, 2014-07-10 at 16:21 -0400, Eoghan Glynn wrote:
> > > One of the issues that has been raised in the recent discussions with
> > > the QA team about branchless Tempest relates to some legacy defects
> > > in the OpenStack notification system.
> >
> > Got links to specifics? I thought the con
On 2014/10/07 22:19, Gregory Haynes wrote:
Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
Hey folks,
after few rounds of reviews and feedbacks, I am sending wireframes,
which are ready for implementation in Juno:
http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09
Good Morning/Day,
I have just started Etherpad
https://etherpad.openstack.org/p/glance-bugday-progress for tracking. Please
also join to #openstack-glance @Freenode to join the chat. All hands onboard
would be appreciated!
BR,
Erno
From: Fei Long Wang [mailto:feil...@catalyst.net.nz]
Sent: 11
On 15/07/14 15:26, Peeyush Gupta wrote:
> I have been trying to set up TripleO. To do that, i first installed
> ironic with devstack. So, I have three baremetal node. Then I went
> on to install tuskar and tuskar-ui using their respective installation
> guides
> i.e. https://github.com/openstack/tu
On 15 July 2014 08:24, Johnson Cheng
wrote:
>
>
> I have two questions here,
>
> 1. It still has “Error encountered during initialization of driver:
> LVMISCSIDriver” error message in cinder-volume.log, how to fix this issue?
>
> 2. From cinder-scheduler.log, it shows “volume service is
Hi Devananda,
thank you for your great feedback and notes. Few reactions follow inline:
On 2014/10/07 21:29, Devananda van der Veen wrote:
Awesome! Glad to see the progress since the design summit.
Some comments:
- slide 1 shows some driver-specific input fields. We have work in
progress to e
HI
As the number of configuration options increases and OpenStack installations
become more complex, the chances of incorrect configuration increases. There is
no better way of enabling cloud providers to be able to check the configuration
state of an OpenStack service than providing a direct R
On Tue, Jul 1, 2014 at 2:32 PM, Nels Nelson
wrote:
> Greetings list,-
>
> Over the next few weeks I will be working on developing additional Tempest
> gating unit and functional tests for the libvirt-lxc compute driver.
>
Tempest is driver agnostic, just like the nova APIs strive to be. As a
con
Hello,
I started a page on the wiki to collect the stories about people
customizing Horizon here:
https://wiki.openstack.org/wiki/Horizon/Customization
I hope that it will help us improve Horizon's customization support in
the areas where people actually care about it, and make it more useful.
I
Dear All,
I can use cinder command to create a volume, but I don't know where to create a
volume from horizon webUI.
>From webUI, I only can delete an existing volume.
Is it right or do I miss something?
Regards,
Johnson
___
OpenStack-dev mailing list
On 14/07/14 09:34, Vaddi, Kiran Kumar wrote:
> Hi,
>
>
>
> In the Juno summit, it was discussed that the existing approach of
> managing multiple VMware Clusters using a single nova compute service is
> not preferred and the approach of one nova compute service representing
> one cluster should
On Thu, Jul 10, 2014 at 01:32:16PM -0700, Devananda van der Veen wrote:
> On Wed, Jul 9, 2014 at 1:58 PM, Matthew Treinish
> wrote:
> >
> > On Wed, Jul 09, 2014 at 10:58:27AM -0400, David Shrewsbury wrote:
> > > Hi!
> > >
> > > The ironic team is working on enabling the API tempest tests with
> ir
On Tue, 2014-07-15 at 08:54 +0100, Henry Nash wrote:
> HI
>
> As the number of configuration options increases and OpenStack
> installations become more complex, the chances of incorrect
> configuration increases. There is no better way of enabling cloud
> providers to be able to check the configu
Hello all,
The miniconf organisers are pleased to announce their first draft of a
schedule for the PyCon Australia OpenStack miniconf:
http://sites.rcbops.com/openstack_miniconf/2014/07/openstack-miniconf-programme-for-pycon-au/
The OpenStack miniconf is a one day conference held on Friday the 1
Le 14/07/2014 20:10, Jay Pipes a écrit :
> On 07/14/2014 10:16 AM, Sylvain Bauza wrote:
>> Le 12/07/2014 06:07, Jay Pipes a écrit :
>>> On 07/11/2014 07:14 AM, John Garbutt wrote:
On 10 July 2014 16:59, Sylvain Bauza wrote:
> Le 10/07/2014 15:47, Russell Bryant a écrit :
>> On 07/10/2
Kyle,
It is probably my fault that I did not notice the review assignment page
beforehand.
Thankfully, I'm already engaged in reviewing the db 'healing' work. On the
other hand, I've barely followed Oleg's progress on the migration work.
I'm ok to assist Maru there, even if I'm surely less suitabl
Andrew,
[2] may be due to agents failing to start. Incorrect agents configuration
will lead to agents unability to start and pacemaker timeouts. [3] I do not
see failures in rabbit service as I see that it succesfully transitioned
from stopped to running state. [4] Swift error shows that you have
Dear Duncan,
Thanks for your reply.
My rootwrap.conf is correct, but I find there is a garbage file at
/etc/cinder/rootwrap.d/ folder.
When I remove it, everything is right.
May I ask you another question that how cinder choose volume node to create
volume if I have multi volume nodes?
For exam
On 15 July 2014 11:59, Johnson Cheng wrote:
> May I ask you another question that how cinder choose volume node to create
> volume if I have multi volume nodes?
>
> For example,
>
> when controller node and compute node are alive, the volume will be created
> at compute node.
>
> When I shutdown c
Mark,
Thanks for your comments (as well as remarks on the WIP code-review).
So clearly gathering and analysing log files is an alternative approach,
perhaps not as immediate as an API call. In general, I believe that the more
capability we provide via easy-to-consume APIs (with appropriate per
On Tue, Jul 15, 2014 at 5:00 AM, Henry Nash
wrote:
> Mark,
>
> Thanks for your comments (as well as remarks on the WIP code-review).
>
> So clearly gathering and analysing log files is an alternative approach,
> perhaps not as immediate as an API call. In general, I believe that the
> more capab
Hi,
I need to pick up my son at 9:00. It’s a short trip. So I will be late about
15 minutes.
Status wise, if everything goes well, the patches should be up in a couple of
days. One of the challenges is due to dividing them up, some unit tests will
fail due to missing module and it took time t
Hi Afef,
There was a regression in Icehouse that broke XenAPI aggregates. This has been
fixed in Juno, however we would recommend you use live migrate with block
migration (using XCP 1.6 or XenServer 6.2 – which is Free as well now, see
http://lists.openstack.org/pipermail/openstack-dev/2013-S
Hi all,
I have been trying to set up tripleO on a ubuntu 12.04 virtual machine.
Now i am following this guide:
http://docs.openstack.org/developer/tripleo-incubator/devtest.html
Now, when I run devtest_testenv.sh command, I get the following error:
error: internal error Network is already in us
On 7/15/2014 12:36 AM, Sean Dague wrote:
On 07/14/2014 07:44 PM, Matt Riedemann wrote:
Today we only gate on exercises in devstack for cells testing coverage
in the gate-devstack-dsvm-cells job.
The cells tempest non-voting job was moving to the experimental queue
here [1] since it doesn't wo
On Tue, Jul 15, 2014 at 5:00 AM, Salvatore Orlando wrote:
> Kyle,
>
> It is probably my fault that I did not notice the review assignment page
> beforehand.
> Thankfully, I'm already engaged in reviewing the db 'healing' work. On the
> other hand, I've barely followed Oleg's progress on the migrat
On 7/15/2014 3:51 AM, Mark McLoughlin wrote:
> On Fri, 2014-07-11 at 10:04 +0100, Chris Dent wrote:
>> On Fri, 11 Jul 2014, Lucas Alvares Gomes wrote:
>>
>>> The data format that Ironic will send was part of the spec proposed
>>> and could have been reviewed. I think there's still time to change it
[1] fixed in https://review.openstack.org/#/c/107046/
Thanks for report a bug.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Joe,
I'd imagine an API like this would be pretty useful for some of these config
tools - so I'd imagine they might well be consumers of this API.
Henry
On 15 Jul 2014, at 13:10, Joe Gordon wrote:
>
>
>
> On Tue, Jul 15, 2014 at 5:00 AM, Henry Nash wrote:
> Mark,
>
> Thanks for your comme
On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote:
> On 07/14/2014 11:47 AM, Steven Hardy wrote:
> >Hi all,
> >
> >I'm probably missing something, but can anyone please tell me when devstack
> >will be moving to keystone v3, and in particular when API auth_token will
> >be configured such
if you are wondering why ofagent CI ("Neutron Ryu") reported a failure
(non-voting) for your review recently, you can probably safely ignore it.
sorry for inconvenience.
the CI has been fixed recently.
unfortunately ofagent on master is broken (a consequence of the broken CI)
and the CI started de
On 7/14/2014 5:28 PM, Matt Riedemann wrote:
On 7/14/2014 5:18 PM, Ben Nemec wrote:
On 07/14/2014 04:21 PM, Matt Riedemann wrote:
On 7/14/2014 4:09 PM, Matt Riedemann wrote:
I opened bug 1341777 [1] against glance but it looks like it's due to
the default log level for requests.packages.u
On 15 July 2014 15:01, Erlon Cruz wrote:
>> Leave the option about when to submit a design vs. when to submit code to
>> the contributor.
>
> That's is what is being done so far right? Hard to know (mainly if you are a
> first contributor) when a change is big or not. I can see lots of patches
> b
On Tue, Jul 15, 2014 at 6:57 AM, Henry Nash
wrote:
> Joe,
>
> I'd imagine an API like this would be pretty useful for some of these
> config tools - so I'd imagine they might well be consumers of this API.
>
This may solve the OpenStack case, but something like this wouldn't solve
the general is
I've been looking at bug 1341777 since yesterday originally because of
g-api logs and this warning:
"HttpConnectionPool is full, discarding connection: 127.0.0.1"
But that's been around awhile and it sounds like an issue with
python-swiftclient since it started using python-requests (see bug 1
On Tuesday, July 15, 2014, Steven Hardy wrote:
> On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote:
> > On 07/14/2014 11:47 AM, Steven Hardy wrote:
> > >Hi all,
> > >
> > >I'm probably missing something, but can anyone please tell me when
> devstack
> > >will be moving to keystone v3, an
Hi All,
Since this issue came up from TLS capabilities RST doc review, I opened a ML
thread for it to make the decision.
Currently, the document says:
"
For SNI functionality, tenant will supply list of TLS containers in specific
Order.
In case when specific back-end is not able to support SNI c
On Tue, 2014-07-15 at 13:00 +0100, Henry Nash wrote:
> Mark,
>
>
> Thanks for your comments (as well as remarks on the WIP code-review).
>
>
> So clearly gathering and analysing log files is an alternative
> approach, perhaps not as immediate as an API call. In general, I
> believe that the mo
On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi
wrote:
> if you are wondering why ofagent CI ("Neutron Ryu") reported a failure
> (non-voting) for your review recently, you can probably safely ignore it.
> sorry for inconvenience.
>
> the CI has been fixed recently.
> unfortunately ofagent on ma
> Leave the option about when to submit a design vs. when to submit code to
the
> contributor.
That's is what is being done so far right? Hard to know (mainly if you are
a first contributor) when a change is big or not. I can see lots
of patches being submitted without the spec getting rejected
> On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi
> wrote:
>> if you are wondering why ofagent CI ("Neutron Ryu") reported a failure
>> (non-voting) for your review recently, you can probably safely ignore it.
>> sorry for inconvenience.
>>
>> the CI has been fixed recently.
>> unfortunately ofa
On Tue, Jul 15, 2014 at 10:25 AM, Mark McLoughlin wrote:
> On Tue, 2014-07-15 at 13:00 +0100, Henry Nash wrote:
>> Mark,
>>
>>
>> Thanks for your comments (as well as remarks on the WIP code-review).
>>
>>
>> So clearly gathering and analysing log files is an alternative
>> approach, perhaps not a
Hi Paul, thanks for your reply. Comments inline.
BTW, is there any way to reply inline instead of top-posting? On these
longer emails, it gets hard sometimes to follow your reply to specific
things I mentioned (vs. what John G mentioned).
Death to MS Outlook.
On 07/14/2014 04:40 PM, Murray, Pau
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
2014-07-14 20:57 GMT-07:00 Dugger, Donald D :
> 1) Forklift (Tasks & status)
> 2) Opens
>
> --
> D
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
thx
debo
On Tue, Jul 15, 2014 at 2:50 AM, Sylvain Bauza wrote:
> Le 14/07/2014 20:10, Jay Pipes
Hi,
My impression was that the frontend would extract the names and hand them to
the driver. This has the following advantages:
* We can be sure all drivers can extract the same names
* No duplicate code to maintain
* If we ever allow the user to specify the names on
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
debo
On Mon, Jul 14, 2014 at 7:25 PM, Yathiraj Udupi (yudupi)
wrote:
> Hi all,
>
> Adding to the
On Jul 15, 2014, at 9:24 AM, Evgeny Fedoruk wrote:
> The question is about SCN and SAN extraction from X509.
> 1. Extraction of SCN/ SAN should be done while provisioning and not
> during TLS handshake
Yes that makes the most sense. If some strange backend really wants to
repeatedly e
Hi,
I think that the discussion have asked that obtaining information out of the
x509 via the SAN field will not be defined as mandatory.
For example Radware's backend extracts this information from the x509 in the
(virtual) device itself, specifying dns values different than what exists in
th
Unfortunately, much as I agree with your sentiment (Death to MS Outlook) my IT
overlords have pretty much forced me into using it. I still top post but try
and use some copied context (typically by adding an `in re:' to be explicit) so
you know what part of the long email I'm referring to.
--
Hi folks, we’ve been talking about this in IRC, but I wanted to bring it to the
ML to get broader feedback and make sure everyone is aware. We’d like to change
our meeting time to better accommodate folks that live around the globe.
Proposals:
Tuesdays, 1900 UTC
Wednessdays, 2000 UTC
Wednessday
On 07/14/2014 12:10 PM, Jay Pipes wrote:
On 07/14/2014 10:16 AM, Sylvain Bauza wrote:
From an operator perspective, people waited so long for having a
scheduler doing "scheduling" and not only "resource placement".
Could you elaborate a bit here? What operators are begging for the
scheduler
We had a short discussion and decided to implement this feature for 5.1 in
this way:
1. Do not store credentials at all even in browser
2. Do not implement specific handling of auth errors
3. Make the form hidden by default; it can be shown by clicking a button
4. There will be a short
On Jul 15, 2014, at 10:55 AM, Samuel Bercovici
wrote:
> Hi,
>
>
> Obtaining the domain name from the x509 is probably more of a
> driver/backend/device capability, it would make sense to have a library that
> could be used by anyone wishing to do so in their driver code.
You can do wh
Hi,
The AMQP 1.0 blueprint proposed for oslo.messaging Juno [0] introduces
dependencies on a few packages that provide AMQP functionality.
These packages are:
* pyngus - a client API
* python-qpid-proton - the python bindings for the Proton AMQP library
* qpid-proton: the AMQP 1.0 library.
pyng
On Tue, Jul 15, 2014 at 1:03 PM, Ken Giusti wrote:
> Hi,
>
> The AMQP 1.0 blueprint proposed for oslo.messaging Juno [0] introduces
> dependencies on a few packages that provide AMQP functionality.
>
> These packages are:
>
> * pyngus - a client API
> * python-qpid-proton - the python bindings for
+1 to German's and Carlos' comments.
It's also worth pointing out that some UIs will definitely want to show SAN
information and the like, so either having this available as part of the
API, or as a standard library we write which then gets used by multiple
drivers is going to be necessary.
If w
And the link, since I forgot it before:
https://github.com/cybertron/oslo.serialization
On 07/14/2014 04:59 PM, Ben Nemec wrote:
> Hi oslophiles,
>
> I've (finally) started the graduation of oslo.serialization, and I'm up
> to the point of having a repo on github that passes the unit tests.
>
>
LGTM. I did leave one comment [1], but it can wait until after the
repo is imported.
Doug
[1]
https://github.com/cybertron/oslo.serialization/commit/af8fafcf34762898e9e19199690a1d636f5fe748
On Tue, Jul 15, 2014 at 1:42 PM, Ben Nemec wrote:
> And the link, since I forgot it before:
> https://g
On 14/07/14 12:21, Tomas Sedovic wrote:
On 12/07/14 06:41, Zane Bitter wrote:
On 11/07/14 09:37, Tomas Sedovic wrote:
[snip]
3. List of IP addresses of all controllers:
https://github.com/openstack/tripleo-heat-templates/blob/a7f2a2c928e9c78a18defb68feb40da8c7eb95d6/overcloud-source.yaml#L4
Excerpts from Jaromir Coufal's message of 2014-07-15 07:15:12 +:
> On 2014/10/07 22:19, Gregory Haynes wrote:
> > Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
> >> Hey folks,
> >>
> >> after few rounds of reviews and feedbacks, I am sending wireframes,
> >> which are rea
On 15/07/14 20:01, Zane Bitter wrote:
> On 14/07/14 12:21, Tomas Sedovic wrote:
>> On 12/07/14 06:41, Zane Bitter wrote:
>>> On 11/07/14 09:37, Tomas Sedovic wrote:
>
[snip]
>
>>>
Alternatively, we could extend the ResourceGroup's get_attr behaviour:
{get_attr: [controller_gr
LGTM.
I'd be interesting in the future to see if we can transparently use some other
serialization format (besides json)...
That's my only compliant is that jsonutils is still named jsonutils instead of
'serializer' or something else but I understand the reasoning why...
-Josh
On Jul 15, 2014
2014-07-15 13:20 GMT-03:00 Kurt Griffiths :
> Hi folks, we’ve been talking about this in IRC, but I wanted to bring it
> to the ML to get broader feedback and make sure everyone is aware. We’d
> like to change our meeting time to better accommodate folks that live
> around the globe. Proposals:
>
Thanks for your response, Joe.
Am I understanding you correctly that the Hypervisor Support Status does
not in fact hinge on any particular Tempest tests, but rather, simply on
individual tests for the libvirt-lxc driver used for gating?
Also, one last question, am I using the incorrect [subheade
Hi all,
Some friendly reminders from your Blueprint Czar...
Juno-2 is just over a week away:
https://launchpad.net/nova/+milestone/juno-2
I have moved most blueprints that don't have all their code ready to
be reviewed to Juno-3. Reviewers, if something is really not going to
make it for Juno-2
On 07/15/2014 09:02 AM, Dugger, Donald D wrote:
> Unfortunately, much as I agree with your sentiment (Death to MS
> Outlook) my IT overlords have pretty much forced me into using it.
It's been a while since I had to deal with really awful software but
since the is a common problem, shall we coll
Hi,
I was working on the last patch that I’d planned to submit for SR-IOV. It
turned out this patch would depend on multiple existing patches. “git review
–d” seems to be supporting one dependency only. Do let me know how we can
create a patch that depends on multiple existing patches under rev
I’ll go with B.
Cheers,
Sriram Madapusi Vasudevan
On Jul 15, 2014, at 2:45 PM, Victoria Martínez de la Cruz
mailto:victo...@vmartinezdelacruz.com>> wrote:
2014-07-15 13:20 GMT-03:00 Kurt Griffiths
mailto:kurt.griffi...@rackspace.com>>:
Hi folks, we’ve been talking about this in IRC, but I wa
Hi folks!
I've noticed progress on the flavor framework discussion slowing down over
the last week. We would really like to see this happen for Juno because
it's critical for many of the features we'd also like to get into Juno for
LBaaS. I understand there are other Neutron extensions which will
On 07/15/2014 03:12 PM, Robert Li (baoli) wrote:
> Hi,
>
> I was working on the last patch that I’d planned to submit for SR-IOV.
> It turned out this patch would depend on multiple existing patches. “git
> review –d” seems to be supporting one dependency only. Do let me know
> how we can create a
Hi All,
The Group Policy team is planning to meet on July 24th to focus on
making progress with the pending items for Juno, and also to
facilitate the vendor drivers. The specific agenda will be posted on
the Group Policy wiki:
https://wiki.openstack.org/wiki/Neutron/GroupPolicy
Prasad Vellanki f
On 09/07/14 16:52, Clint Byrum wrote:
> Hello!
>
> I've been looking at the statistics, and doing a bit of review of the
> reviewers, and I think we have an opportunity to expand the core reviewer
> team in TripleO. We absolutely need the help, and I think these two
> individuals are well position
I think I've provided some examples in the review.
However, the point is mostly to simplify usage from a user perspective -
allowing consumers of the neutron API to use the same flavour object for
multiple services.
There are other considerations which could be made, but since they're
dependent on
The Barbican development team would like to announce the release of
python-barbicanclient version 2.2.1
python-barbicanclient is a client library for the Barbican Key Management
Service. It provides a Python API (barbicanclient module) and a
command-line tool (barbican).
This release can be inst
B
Wednessdays, 2100 UTC
Wednessdays, 2000 UTC
Tuesdays, 1900 UTC
On Tue, Jul 15, 2014 at 12:12 PM, Sriram Madapusi Vasudevan <
sriram.madapusiva...@rackspace.com> wrote:
> I’ll go with B.
>
> Cheers,
> Sriram Madapusi Vasudevan
>
>
>
> On Jul 15, 2014, at 2:45 PM, Victoria Martínez de la Cr
On Tue, Jul 15, 2014 at 07:20:47AM -0700, Morgan Fainberg wrote:
>We just did a test converting over the default to v3 (and falling back to
>v2 as needed, yes fallback will still be needed) yesterday (Dolph posted a
>couple of test patches and they seemed to succeed - yay!!)A It looks
Hello!
I'm new to both Swift and OpenStack, I hope you can help me.
Considering statsd is enabled, each time something is logged, a new socket
is being opened.
At least, this is what I understood from the implementation and usage of
StatsdClient at:
- swift/common/utils.py
- swift/common/middlew
> Thanks for the info - any chance you can provide links to the relevant
> reviews here? If so I'll be happy to pull them and locally test to ensure
> our issues will be addressed :)
>
Sure!
https://review.openstack.org/#/c/106819/ is the change for the
keystonemiddleware package (where the ch
>
> > Thanks for the info - any chance you can provide links to the relevant
> > reviews here? If so I'll be happy to pull them and locally test to ensure
> > our issues will be addressed :)
> >
> Sure!
>
> https://review.openstack.org/#/c/106819/ is the change for the
> keystonemiddleware
Ok, I just released 2.18.1 to address this issue.
https://launchpad.net/python-novaclient/+milestone/2.18.1
Cheers,
Michael
On Sat, Jul 12, 2014 at 7:18 AM, Michael Still wrote:
> I can do another release once https://review.openstack.org/#/c/106447/ merges.
>
> Michael
>
> On Sat, Jul 12, 2014
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15/07/14 20:36, Joshua Harlow wrote:
> LGTM.
>
> I'd be interesting in the future to see if we can transparently use
> some other serialization format (besides json)...
>
> That's my only compliant is that jsonutils is still named jsonutils
> in
Hi,
I have posted a blue print for a subscription mechanism for blazar.
https://blueprints.launchpad.net/blazar/+spec/subscription-mechanism
Appreciate your feedback on the BP.
Regards,
Lakmal
___
OpenStack-dev mailing list
OpenStack-dev@lists.openst
Hi.
We've now hit our room capacity, so I have closed registrations for
the nova mid cycle meetup. Please reply to this thread if that's a
significant problem for someone.
Thanks,
Michael
--
Rackspace Australia
___
OpenStack-dev mailing list
OpenStac
Hi Stephen,
So, as was discussed, existing proposal has some aspects which better to be
postponed, like extension list on the flavor (instead of tags).
Particularly that idea has several drawbacks:
- it makes public API inflexible
- turning features on/off is not what flavors should be doing, it
We've been chatting in IRC, but for the mailing list archives, yes! we'd love
to see patches to improve this.
--John
On Jul 15, 2014, at 1:22 PM, Tatiana Al-Chueyr Martins
wrote:
> Hello!
>
> I'm new to both Swift and OpenStack, I hope you can help me.
>
> Considering statsd is enabled, ea
Clint, thanks heaps for making the time to do a meta-review. With the
clear support of the other cores, I'm really happy to be able to
invite Alexis and JP to core status.
Alexis, Jon - core status means a commitment to three reviews a work
day (on average), keeping track of changing policies and
Thanks Russell for the quick response. I¹ll give it a try rearranging the
dependencies.
‹Robert
On 7/15/14, 3:26 PM, "Russell Bryant" wrote:
>On 07/15/2014 03:12 PM, Robert Li (baoli) wrote:
>> Hi,
>>
>> I was working on the last patch that I¹d planned to submit for SR-IOV.
>> It turned out
Hi Jaromir,
> Excerpts from Jaromir Coufal's message of 2014-07-09 07:51:56 +:
>> Hey folks,
>>
>> after few rounds of reviews and feedbacks, I am sending wireframes,
>> which are ready for implementation in Juno:
>>
>>
http://people.redhat.com/~jcoufal/openstack/juno/2014-07-09_nodes-u
Well, I'll probably get ostracized for this, but I actually prefer top posting
(I like RPN calculators also, I'm just warped that way). I `really` dislike
paging through 10 screens of an email to discover the single comment buried
somewhere near the end. With top posting the new content is alw
Hi
I haven't registered yet unfortunately can you squeeze in one more person?
Chuck
Original message From: Michael Still
Date:07-15-2014 4:56 PM (GMT-05:00)
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova]
Registration for the mid cycle meetup is
Hi,
This patch was initially uploaded on Jun 27, 2014 and we have got a number of
reviews from the community. A lot of thanks to these who kindly reviewed and
provided feedback.
Can the neutron cores please review/approve it so we can make progress here?
Really appreciate your attention and h
Hi Salvatore and Eugene,
Responses inline:
On Tue, Jul 15, 2014 at 12:59 PM, Salvatore Orlando
wrote:
> I think I've provided some examples in the review.
>
I was hoping for specific examples. The discussion I've seen so far has
been vague enough that it's difficult to see what people mean. It
Hi Eugene,
I understand the argument with preferring tags over extensions to turn/features
on and off since that is more fine grained. Now you are bringing up the policy
framework to actually controlling which features are available. So let’s look
at this example:
As an operator I want to offe
Hi Stephen,
+1
Admittedly, since Stephen and I come from an operator centric world we have
sometimes trouble grasping other use cases so I am wondering if you can provide
one which would help us understand the need for grouping multiple different
devices (LB, VPN, FW) under a single flavor.
Hi Michael,
I was planning to attend the meet up, and was going to register today.
Based on today¹s Nova/Gantt discussions in gantt subgroup meeting, it
would be really helpful to meet in person with the folks involved with
Gantt efforts.
Can you please make an exception and allow one more regi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/07/14 22:48, Vishvananda Ishaya wrote:
>
> On Jul 13, 2014, at 9:29 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 12/07/14 03:17, Mike Bayer wrote:
>>>
>>> On 7/11/14, 7:26 PM, Carl Baldwin wrote:
On Jul 11, 2014 5:3
Hey Michael,
Would love to attend and give an update on where we are with Libvirt+LXC
containers.
We have bunch of patches proposed and more coming down the pike, so would
love to get some feedback on where we are and where we should go with this.
I just found out I was cleared to attend yesterd
I am happy to announce that the first (zero'th?) item in the Neutron Gap
Coverage[1] has merged[2]. The Neutron database now contains all tables for
all plugins, and database migrations are no longer conditional on the
configuration.
In the short term, Neutron developers who write migration script
1 - 100 of 114 matches
Mail list logo
