Nova currently is preventing one from attaching multiple nics on the same
L2. That said I don't think we've clearly determined a use case for having
multiple nics on the same L2. One reason why we don't allow this is doing
so would allow a tenant to easily loop the network and cause a bcast storm
a
Hello Huang.
You are right, that this problem is presented in networks update for
OS::Nova::Server. I have known about it, and I wanted to discuss it with
Steve Baker, but possibly forgot to do it. Thank you, that you raise this
thread.
About issue.
The cause why it happens is simple: when nova
Hi folks,
We'll be having the Sahara team meeting as usual in
#openstack-meeting-alt channel.
Agenda:
https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Agenda_for_April.2C_17
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140417T18
--
Sincerely yours,
Sergey
Hi,
I'm refactoring LDAP driver in Keystone. I have a question:
why do we have no gate job, checking keystone with LDAP?
Are there any reasons not to create the job?
If there aren't I'd like to work on it.
Thanks
Sergey Nikitin
___
OpenStack-dev mailin
> From: Steve Baker
> To: [email protected]
> Date: 17/04/2014 00:55
> Subject: Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest]
> Questions about images
>
> On 17/04/14 09:11, Thomas Spatzier wrote:
> >> From: Mike Spreitzer
> >> To: "OpenStack Development Mailing List
On 17 April 2014 04:02, Aaron Rosen wrote:
> Hi,
>
> Comments inline:
>
>
> On Tue, Apr 8, 2014 at 3:16 PM, Salvatore Orlando wrote:
>
>> I have been recently investigating reports of slowness for list responses
>> in the Neutron API.
>> This was first reported in [1], and then recently was obser
Hi Thomas,
On Tue, Apr 15, 2014 at 01:16:50PM +0200, Thomas Herve wrote:
> Hi all,
>
> I started working on the stack snapshot blueprint [1] and wrote a first
> series of patches [2] to get a feeling of what's possible. I have a couple of
> related design questions though:
>
> * Is a stack sn
Hi Tom,
Thanks for the reminder. I'm not sure if there is anyone from Glance team
working this. But I would like to highlight this in tonight Glance weekly
meeting and I will see what I can do.
Thanks & Best regards,
Fei Long Wang (王飞龙)
confirmed
On 04/17/2014 06:51 AM, John Dickinson wrote:
> I'd like to announce my Technical Committee candidacy.
>
> I've been involved with OpenStack since it began. I'm one of the original
> authors of Swift, and I have been serving as PTL since the position was
> established. I'm employed by
发件人: Sergey Kraynev [mailto:[email protected]]
发送时间: 2014年4月17日 15:35
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev] [Heat][Nova][Neutron]Detach interface will delete the
port
Hello Huang.
You are right, that this problem is presented in networks
There is interesting patch on review
https://review.openstack.org/#/c/77043/15.
I suppose that it's related with discussed problems. Possibly we should
wait when it will be merged and then check mentioned use-cases.
Regards,
Sergey.
On 17 April 2014 12:18, Huangtianhua wrote:
>
>
>
>
> *发件人:*
>IMHO, zero-copy approach is better
VMThunder's "on-demand transferring" is the same thing as your "zero-copy
approach".
VMThunder is uses iSCSI as the transferring protocol, which is option #b of
yours.
>Under #b approach, my former experience from our previous similar
>Cloud deployment (not
On Thu, Apr 17, 2014 at 4:41 PM, lihuiba wrote:
>>IMHO, zero-copy approach is better
> VMThunder's "on-demand transferring" is the same thing as your "zero-copy
> approach".
> VMThunder is uses iSCSI as the transferring protocol, which is option #b of
> yours.
>
IMO we'd better to use backend sto
Well we definitely need a better way to get multiple IP addresses onto one
host. The current steps are terrible for a user and even for an
orchestration system like heat. I can't imagine how convoluted a template
would look to automate that process...
I'm not suggesting multiple NICs is the only a
Hello everyone,
I want to integrate Swift with Nas.
So, I have mounted nas storage on to my linux machine and in the place of
/dev/sdb,
(the device that we specify in swift installation process, I referred this
link for swift installation
http://docs.openstack.org/developer/swift
Thanks Brown, I was using same way as you did but always failed, not sure
if it is caused by my image but the image does work for KVM before convert.
I will try your image later.
Thanks!
2014-04-17 11:04 GMT+08:00 Eric Brown :
> Good timing. I just tried this today for the first time.
> Here'
Hi Daniel,
The intention of image type ('default', 'fast', ' shared',
'sharedfast') look like volume type in cinder. So I think there are two
solutions :
1. Like using volume type to configure a multiple-storage back-end in cinder,
we could extend nova API , then create image-type resour
On Thu, Apr 17, 2014 at 10:06:03AM +, Yuzhou (C) wrote:
> Hi Daniel,
> The intention of image type ('default', 'fast', ' shared',
> 'sharedfast') look like volume
> type in cinder. So I think there are two solutions :
I was explicitly *NOT* considering those names to be standardiz
You're probably going to want to look at the proposals for volume
consistency groups in cinder - backing up/snapshotting volumes
independently is likely to cause issues with some applications, since
different VMs will be in slightly different states, so you can get
lost or duplicated work/records/e
On 17 April 2014 11:11, Zhi Yan Liu wrote:
> As I said currently Nova already has image caching mechanism, so in
> this case P2P is just an approach could be used for downloading or
> preheating for image caching.
>
> I think P2P transferring/pre-caching sounds a good way to go, as I
> mentione
Hello,
Right now I am trying to set-up a self-signup for users of our OpenStack
cloud. One of the essential points of this signup is verification of
user's email address - until a user proves that this address belongs to
him/her, he/she should not be able to do anything useful in the cloud.
I opened blueprint for detailed description about this feature
https://blueprints.launchpad.net/openstack-ci/+spec/nodepool-kvm-backend
> > Hi community!
> > I have a modification for Nodepool which allows to use it with a
> > clean KVM/QEMUhost while still support OpenStack. This allows parallel
Hi Eugene:
I have several questions
1. I wonder if tags is really needed. for example, if I want a ipsec
vpn, I'll define a flavor which is directly refer to ipsec provider.
If using current design, almost all users will end up creating flavors
like this:
ipsec tags=[ipsec]
sslvpn tags=[sslvpn]
Hi Zang,
1.
> so the tags is totally useless, and I suggest replace tags by provider
> name/uuid. It is much more straightforward and easier.
Funny thing is that the goal of flavor framework is directly opposite.
We need to hide provider/vendor name. Ssl vpn or ipsec could be implemented
by differ
Akihiro Motoki wrote:
>To cope with such cases, allowed-address-pairs extension was implemented.
>http://docs.openstack.org/api/openstack-network/2.0/content/allowed_address_pair_ext_ops.html
Question on this in particular: Is a tenant permitted to do this? If so, what
exactly is the iptables
Guys,
Ruslan Kamaldinov has been doing a lot of things for Murano recently
(including devstack integration, automation scripts, making Murano
more compliant with OpenStack standards and doing many reviews). He's
actively participating in our ML discussions as well. I suggest to add
him to the core
Aaron Rosen wrote:
>Sorry not really. It's still not clear to me why multiple nics would be
>required on the same L2 domain.
I’m a fan of this old paper for nostalgic reasons
http://static.usenix.org/legacy/publications/library/proceedings/neta99/full_papers/limoncelli/limoncelli.pdf
but a sea
On Thu, Apr 17, 2014 at 8:07 PM, Eugene Nikanorov
wrote:
> Hi Zang,
>
> 1.
>> so the tags is totally useless, and I suggest replace tags by provider
>> name/uuid. It is much more straightforward and easier.
> Funny thing is that the goal of flavor framework is directly opposite.
> We need to hide
+1
Totally agree
--
Regards,
Alexander Tivelkov
On Thu, Apr 17, 2014 at 4:37 PM, Timur Sufiev wrote:
> Guys,
>
> Ruslan Kamaldinov has been doing a lot of things for Murano recently
> (including devstack integration, automation scripts, making Murano
> more compliant with OpenStack standards
+1
Agree
On Thu, Apr 17, 2014 at 4:51 PM, Alexander Tivelkov
wrote:
> +1
>
> Totally agree
>
> --
> Regards,
> Alexander Tivelkov
>
>
> On Thu, Apr 17, 2014 at 4:37 PM, Timur Sufiev wrote:
>
>> Guys,
>>
>> Ruslan Kamaldinov has been doing a lot of things for Murano recently
>> (including devsta
>IMO we'd better to use backend storage optimized approach to access
>remote image from compute node instead of using iSCSI only. And from
>my experience, I'm sure iSCSI is short of stability under heavy I/O
>workload in product environment, it could causes either VM filesystem
>to be marked as rea
On 04/16/2014 07:56 PM, Dan Smith wrote:
>> Do we really want to -1 for spelling mistake in nova-specs?
>
> I do, yes. These documents are intended to be read by deployers and
> future developers. I think it's really important that they're useful in
> that regard.
Guys, use your judgement with th
glance-bittorrent-delivery and VMThunder have similar goals fast
provisioning
of large amount of VMs, and they share some ideas like P2P transferring, but
they
go with different techniques.
VMThunder only downloads data blocks that are really used by VMs, so as to
reduce bandwith and tim
Brandon,
Towards the bottom of that document it does mention content switching and
> how it would work with this. I know its a huge text document and hard to
> navigate but it is there.
>
Yeah, i should have been more specific. My concern is that 'single-call
API' is not powerfull enough right
>> A question about the fix from https://review.openstack.org/#/c/82931
> Also, how does this work for RHEL-based distros where they tend to backport
> new kernel features? For instance vxlan support was added in the kernel for
> RHEL6.5 which is 2.6.32-based... That changeset looks like it breaks
On Thu, Apr 17, 2014 at 9:14 AM, Terry Wilson wrote:
>>> A question about the fix from https://review.openstack.org/#/c/82931
>
>> Also, how does this work for RHEL-based distros where they tend to backport
>> new kernel features? For instance vxlan support was added in the kernel for
>> RHEL6.5 w
+1
On Thu, Apr 17, 2014 at 6:01 AM, Dmitry Teselkin wrote:
> +1
>
> Agree
>
>
> On Thu, Apr 17, 2014 at 4:51 PM, Alexander Tivelkov <
> [email protected]> wrote:
>
>> +1
>>
>> Totally agree
>>
>> --
>> Regards,
>> Alexander Tivelkov
>>
>>
>> On Thu, Apr 17, 2014 at 4:37 PM, Timur Sufiev wro
+1
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Thu, Apr 17, 2014 at 6:51 PM, Georgy Okrokvertskhov <
[email protected]> wrote:
> +1
>
>
> On Thu, Apr 17, 2014 at 6:01 AM, Dmitry Teselkin
> wrote:
>
>> +1
>>
>> Agree
>>
>>
>> On Thu, Apr 17, 2014 at 4:51
+1
On Thu, Apr 17, 2014 at 7:11 PM, Stan Lagun wrote:
> +1
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
>
> On Thu, Apr 17, 2014 at 6:51 PM, Georgy Okrokvertskhov <
> [email protected]> wrote:
>
>> +1
>>
>>
>> On Thu, Apr 17, 2014 at 6:01 AM, Dmi
Candidate proposals for the Technical Committee positions (7 positions)
will remain open until 05:59 utc April 18, 2014.
That leaves about 14ish hours for any last candidate proposals to still
be eligible.
Be sure to get yours in and confirmed if that is your intention.
The election will begin a
Hey everyone!
I’d like to get your gut reaction on an idea for the future of alarming. Should
I or should I not put it up for debate at the design summit?
---TL;DR
Online algorithms for computing stream statistics over sliding windows would
allow us to provide sample statistics within an error
Hello everyone!
I was originally not going to be able to attend the summit next month, but
things have changed and I would now like to attend. Unfortunately, tickets have
become prohibitively expensive at this point. If any of you have or know anyone
who has a ticket that they are not going to
I second Kyle on this,
Quite more clear for users to see the version error message on the logs!
Edgar
On 4/17/14, 7:23 AM, "Kyle Mestery" wrote:
>On Thu, Apr 17, 2014 at 9:14 AM, Terry Wilson wrote:
A question about the fix from https://review.openstack.org/#/c/82931
>>
>>> Also, how does
Glad to know I wasn't crazy in thinking it would completely break RHEL or
OSes that backport things. I tried pointing this out in the hopes it would
get fixed before Icehouse dropped, but I guess I didn't yell loud enough or
follow-up on my own. Should target fixing for the first stable release a
Andrew,
While i agree there is a thought to change/improve this in future, but
the way it is today isn't acceptable, mainly bcos (as i said) the new
serverIP is taken effect w/o service restart and if someone adds -o
options.. even after service restart it doesn't take effect. Its confusing
to t
On Fri, Apr 11, 2014 at 8:25 PM, Eric Harney wrote:
> On 04/11/2014 07:54 AM, Deepak Shetty wrote:
> > Hi,
> >I am using the nfs and glusterfs driver as reference here.
> >
> > I see that load_shares_config is called everytime via
> > _ensure_shares_mounted which I feel is incorrect mainly be
Hello All. The OpenStack infra team has been working to put
everything in place so that we can upgrade review.o.o from Gerrit
version 2.4.4 to version 2.8.4 We are happy to announce that we are
finally ready to make it happen!
We will begin the upgrade on Monday, April 28th at 1600 UTC (the
Open
On Thu, Apr 17, 2014 at 10:00 PM, Deepak Shetty wrote:
>
>
>
> On Fri, Apr 11, 2014 at 8:25 PM, Eric Harney wrote:
>
>> On 04/11/2014 07:54 AM, Deepak Shetty wrote:
>> > Hi,
>> >I am using the nfs and glusterfs driver as reference here.
>> >
>> > I see that load_shares_config is called every
On Tue, Apr 15, 2014 at 4:14 PM, Duncan Thomas wrote:
> On 11 April 2014 16:24, Eric Harney wrote:
>
>
> > I suppose I should also note that if the plans in this blueprint are
> > implemented the way I've had in mind, the main issue here about only
> > loading shares at startup time would be in p
On Thu, Apr 17, 2014 at 9:41 AM, Stefano Maffulli wrote:
> Please don't -1 if it's a minor grammar/spelling mistake that doesn't
> prevent proper understanding of the blueprint by a person skilled in the
> art.
>
or it may be acceptable that the reviewer can always do the minor spelling
correcti
Hi all,
I am trying to setup OpenStack on Ubuntu 12.04 using devstack. Here is the
error I am getting:
Setting up rabbitmq-server (2.7.1-0ubuntu4) ...
Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err}
rabbitmq-server.
invoke-rc.d: initscript rabbitmq-server, action "
Hi ,
how to authenticate against openstack's Ceilometer Client using python
program?
plase i need response please
Sincerly ,
Chraiti Hachem
software enginee
___
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org
Hello,
I am trying to make sure that a user can't do anything useful with an
unscoped token, and got to the following code in
keystoneclient.middleware.auth_token:
if _token_is_v2(token_info) and not auth_ref.project_id:
raise InvalidUserToken('Unable to determine tenancy.
On Apr 17, 2014, at 8:45 AM, Eugene Nikanorov
mailto:[email protected]>>
wrote:
Brandon,
Towards the bottom of that document it does mention content switching and how
it would work with this. I know its a huge text document and hard to navigate
but it is there.
Yeah, i should have b
On Thu, Apr 17, 2014 at 6:07 PM, CARVER, PAUL wrote:
> Aaron Rosen wrote:
>
> >Sorry not really. It's still not clear to me why multiple nics would be
> required on the same L2 domain.
>
>
>
> I’m a fan of this old paper for nostalgic reasons
> http://static.usenix.org/legacy/publications/libra
On Fri, Apr 11, 2014 at 7:29 PM, Duncan Thomas wrote:
> On 11 April 2014 14:21, Deepak Shetty wrote:
> > My argument was mostly from the perspective that unmanage shud do its
> best
> > to revert back the volume to its original state (mainly the name).
> >
> > Like you said, once its given to cin
Shaunak, these are some good questions. Input from the docs team would
be useful for some of these as well.
On Wed, Apr 16, 2014 at 10:06 PM, Shaunak Kashyap
wrote:
> Hi folks,
>
> As part of working on
> https://blueprints.launchpad.net/openstack-sdk-php/+spec/sphinx-docs, I’ve
> been looking
Hi all,
The discussion of blueprint review has come up recently for several
reasons, not the least of which is that I haven't yet reviewed many of the
blueprints that have been filed recently.
My biggest issue with launchpad blueprints is that they do not provide a
usable interface for design ite
Hi,
Can someone help me understand why Jenkins build shows failures
for some of the tests for my patch @
https://review.openstack.org/#/c/86888/
I really couldn't understand it even after clicking those links
TIA
thanx,
deepak
___
OpenStack-dev mailin
Yesterday I re-submitted a patchset to Gerrit after updating the some comments
in a function header and the documentation in docs. So I didn't make any code
changes and my previous changeset passed all the Jenkins tests, but this time
it failed the check-grenade-dsvm-neutron and the
check-tempe
All,
We have a couple IPv6 design summit sessions that have been registered,
and at least one of them is in a pre-approved state:
http://summit.openstack.org/cfp/details/21
We'll have at least 40 minutes to discuss a roadmap for IPv6 in the
coming Juno cycle.
I have created an etherpad, and wou
Doh!
Nevermind, I think I figured it out with more careful reading, sorry for the
unnecessary email.
From: Pecoraro, Alex [mailto:[email protected]]
Sent: Thursday, April 17, 2014 10:21 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Swift] Elastic Recheck failure?
Yeste
I believe the exchange should also be ‘nova’.
Vish
On Apr 15, 2014, at 11:31 PM, Prashant Upadhyaya
wrote:
> Hi Vish,
>
> Thanks, now one more question –
>
> When I send the request out, I send it to the exchange ‘nova’ and routing key
> ‘conductor’ (using RabbitMQ), this will take the me
On Thu, Apr 17, 2014 at 12:26 PM, Collins, Sean
wrote:
> All,
>
> We have a couple IPv6 design summit sessions that have been registered,
> and at least one of them is in a pre-approved state:
>
> http://summit.openstack.org/cfp/details/21
>
> We'll have at least 40 minutes to discuss a roadmap fo
On Thu, Apr 17, 2014 at 12:11 PM, Devananda van der Veen
wrote:
> Hi all,
>
> The discussion of blueprint review has come up recently for several reasons,
> not the least of which is that I haven't yet reviewed many of the blueprints
> that have been filed recently.
>
> My biggest issue with launc
Howdy folks!
Based on this morning's IRC meeting, it seems to me there's some contention
and confusion over the need for "single call" functionality for load
balanced services in the new API being discussed. This is what I understand:
* Those advocating "single call" are arguing that this simplif
Personally, I try not to be disagreeable and to be considerate in my
reviews. However, I don't want to worry too much about hurting
someone's feelings by making a comment. As a community we should be
considerate and polite but we should also embrace critical reviews of
our own work.
I think addi
I'd prefer that others *not* upload a new patch over mine just to make
a spelling correction. I might be in the middle of another version of
the patch myself and mine will overwrite yours. If you want to upload
a patch over mine please ask me first so that we can coordinate and
discuss the change
Hi,
quickly said, you can use the client API with something like:
import keystoneclient.v2_0.client as ksclient
creds = {‘username’:’demo’, ‘password’:’password’, ‘auth_url’:’’, ‘tenant_name’:’demo’}
keystone = ksclient.Client(**creds)
import ceilometerclient.v2.client as cclient
then jenkins failure seems to indicate that jenkins xUnit plugin could
not find any test result files for processing. it could be that the
test didn't get run or that it ran but didn't generate the rest
results required for the plugin to pick up? that's probably where i
would check.
On Thu, Apr
Sure thing [1]. The easiest change I saw was to remove the
restriction that the number of sub titles is exactly 9. This won't
require any of the other blueprints already posted for review to
change. See what you think.
Carl
[1] https://review.openstack.org/#/c/88381/
On Wed, Apr 16, 2014 at 3
I don't see any indication that a floating ip can be associated with
any of the secondary addresses. Can this be done?
If not, then multiple addresses are not useful if a floating ip is
required to make the server public facing.
Carl
On Wed, Apr 16, 2014 at 10:46 PM, Aaron Rosen wrote:
> The a
Hi Devs,
I'm not getting any answer for my questions from the openstack general alias
for my question about the new enhancement done by Zhi Yan Liu (copied again
below). Does anyone here know the answers or know where to check in the code
for this enhancement?
"Zhi,
Could you please confirm i
hello Stephen,
I am interested in LBaaS and want to know if we post the weekly meeting's
chat transcripts online?
or may be update an etherpad?
Can you please share the links?
thanks,
SriD
--
View this message in context:
http://openstack.10931.n7.nabble.com/Neutron-LBaas-Single-call-API-d
hello Stephen,
I am interested in LBaaS and want to know if we post the weekly meeting's
chat transcripts online?
or may be update an etherpad?
Can you please share the links?
thanks,
SriD
--
View this message in context:
http://openstack.10931.n7.nabble.com/Neutron-LBaas-Single-call-API-d
Hi Sri,
Yes, the meeting minutes & etc. are all available here, usually a few
minutes after the meeting is over:
http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/
(You are also, of course, welcome to join!)
Stephen
On Thu, Apr 17, 2014 at 11:34 AM, Sri wrote:
> hello Stephen,
>
>
>
I would like to announce my candidacy for the Technical Committee this
term.
Background
=
I began working on OpenStack more than two years ago. Initially, I focused
on improving Nova's database API and led the Nova DB team in that cleanup
effort for a time. As much of that work was finis
confirmed
On 04/17/2014 02:48 PM, Devananda van der Veen wrote:
> I would like to announce my candidacy for the Technical Committee this
> term.
>
>
> Background
> =
>
> I began working on OpenStack more than two years ago. Initially, I focused
> on improving Nova's database API and led
Per blueprint
https://blueprints.launchpad.net/horizon/+spec/merge-sahara-dashboard we are
merging the Sahara Dashboard UI code into the Horizon code base.
Over the last week, I have been working on making this merge happen and along
the way some interesting questions have come up. Hopefully,
Guys,
I here thinking about IPSec when with IPv6 and, one of the first
ideas/wishes of IPv6 scientists, was to always deploy it with IPSec
enabled, always (I've heard). But, this isn't well diffused by now. Who is
actually using IPv6 Opportunistic Encryption?!
For example: With O.E., we'll be abl
On Thu, Apr 17, 2014 at 1:18 PM, Carl Baldwin wrote:
> Sure thing [1]. The easiest change I saw was to remove the
> restriction that the number of sub titles is exactly 9. This won't
> require any of the other blueprints already posted for review to
> change. See what you think.
>
This was a go
Oh! One other question:
5. Should "single-call" stuff work for the lifecycle of a load balancing
service? That is to say, should "delete" functionality also clean up all
primitives associated with the service?
On Thu, Apr 17, 2014 at 11:44 AM, Stephen Balukoff wrote:
> Hi Sri,
>
> Yes, the meet
Wow, easiest merge ever! Can we get this repository counted in our stats?! ;)
Carl
On Thu, Apr 17, 2014 at 1:09 PM, Kyle Mestery wrote:
> On Thu, Apr 17, 2014 at 1:18 PM, Carl Baldwin wrote:
>> Sure thing [1]. The easiest change I saw was to remove the
>> restriction that the number of sub t
Completely agree.
We're spending too much time discussing features after they're implemented,
which makes contribution more difficult for everyone. Forcing an explicit
design+review process, using the same tools as we use for coding+review
seems like a great idea. If it doesn't work we can iterate
For those following the dockenstack work, just giving an update that it has
finally been updated to work with the nova-docker stackforge repository.
The new image is now available on the docker index and may be fetched with
'docker pull ewindisch/dockenstack'. Usage instructions are available in
th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sample Keystone v3 policy exposes privilege escalation vulnerability
- ---
### Summary ###
The policy.v3cloudsample.json sample Keystone policy file combined with
the underlying mutability of the domain ID for user, group, and project
entities exposed
On 04/17/2014 06:37 AM, CARVER, PAUL wrote:
Aaron Rosen wrote:
Sorry not really. It's still not clear to me why multiple nics would be
required on the same L2 domain.
I’m a fan of this old paper for nostalgic reasons
http://static.usenix.org/legacy/publications/library/proceedings/neta99/full
Hi everyone,
I'm glad to announce the final release of Sahara 2014.1 "Icehouse".
During this cycle we've completed 58 blueprint and fixed 124 bugs.
You can find source tarballs with complete lists of features and bug fixes:
https://launchpad.net/sahara/icehouse/2014.1
Release notes contain an o
This review seems to suggest that it can be done:
https://review.openstack.org/#/c/85432
I was not able to reproduce this in devstack. How does this work? My
nova command to add an IP return success but didn't seem to actually
add an IP address to the instance and did not show in neutron
port-s
+1
> On Apr 17, 2014, at 12:27 PM, Russell Haering
> wrote:
>
> Completely agree.
>
> We're spending too much time discussing features after they're implemented,
> which makes contribution more difficult for everyone. Forcing an explicit
> design+review process, using the same tools as we us
If you'd like to have a go at implementing this in nova's Juno
release, then you need to create a new-style blueprint in the
nova-specs repository. You can find more details about that process at
https://wiki.openstack.org/wiki/Blueprints#Nova
Some initial thoughts though, some of which have alrea
Hi Stephen,
1. Could you please explain what you understand single-call API functionality
to be?
From my perspective most of our users will likely create load balancers via a
web interface. Thought not necessary, having a single API call makes it easier
to develop the web interface.
For the “
2014-04-17 21:30 GMT+02:00 Eric Windisch :
>
> Furthermore, I've started testing KVM/Qemu support. It's looking
> promising. It's too early to claim it's supported, but I've only ran into
> minor issues so far. I'll update again when I've made further progress.
> Also pending, but not far away, i
Replied as inline comments.
On Thu, Apr 17, 2014 at 9:33 PM, lihuiba wrote:
>>IMO we'd better to use backend storage optimized approach to access
>>remote image from compute node instead of using iSCSI only. And from
>>my experience, I'm sure iSCSI is short of stability under heavy I/O
>>workload
A few reminders about design summit sessions for Heat...
* The deadline for proposals is the 20th of April, i.e. the end of this
week. Get your proposals in now.
* The Design Summit isn't the place to introduce feature proposals. The
place to introduce proposals is the mailing list and there'
On Fri, Apr 18, 2014 at 5:19 AM, Michael Still wrote:
> If you'd like to have a go at implementing this in nova's Juno
> release, then you need to create a new-style blueprint in the
> nova-specs repository. You can find more details about that process at
> https://wiki.openstack.org/wiki/Blueprin
I’m going to try to not lose my cool here, but I’m extremely upset by this.
In December, oslo apparently removed the code for ‘use_tpool’ which allows you
to run DB calls in Threads because it was ‘eventlet specific’. I noticed this
when a review was posted to nova to add the option within nova
On Apr 17, 2014, at 2:11 PM, Stephen Balukoff
mailto:[email protected]>>
wrote:
Oh! One other question:
5. Should "single-call" stuff work for the lifecycle of a load balancing
service? That is to say, should "delete" functionality also clean up all
primitives associated with the service
Stephen,
I have responded to your questions below.
On 04/17/2014 01:02 PM, Stephen Balukoff wrote:
Howdy folks!
Based on this morning's IRC meeting, it seems to me there's some
contention and confusion over the need for "single call" functionality
for load balanced services in the new API bei
Heyas, y'all!
So, given both the prioritization and usage info on HA functionality for
Neutron LBaaS here:
https://docs.google.com/spreadsheet/ccc?key=0Ar1FuMFYRhgadDVXZ25NM2NfbGtLTkR0TDFNUWJQUWc&usp=sharing
It's clear that:
A. HA seems to be a top priority for most operators
B. Almost all load
1 - 100 of 121 matches
Mail list logo
