Hi Brad
> To me, a global range that everyone is using that's provided by OpenStack is
> seems much worse than just calculating an arbitrary private range by flipping
> bit b2 to 1 as shown in the wiki article below. As long as you set this,
> you're guaranteed not to collide with any register
Hi Stef
I thnk @lists.openstack.org is a good.branding compare to @launchpad.net
Frans Thamura
Meruvian
On Oct 21, 2012 9:24 AM, "Stefano Maffulli" wrote:
> [I realized now I replied privately only. This meant to be public.]
>
> On Fri 12 Oct 2012 02:13:54 PM PDT, Frans Thamura wrote:
>
>> is t
[I realized now I replied privately only. This meant to be public.]
On Fri 12 Oct 2012 02:13:54 PM PDT, Frans Thamura wrote:
is this mailing list move to the new mailing list?
Yes, it will move to lists.openstack.org as soon as possible.
Here is what needs to happen:
- export list of subscri
On 10/20/2012 01:50 PM, heckj wrote:
I sent this to the openstack-dev list, and thought I'd double post
this onto the openstack list at Launchpad for additional feedback.
-joe
Begin forwarded message:
*From: *heckj mailto:he...@mac.com>>
*Subject: **[openstack-dev] [keystone] Tokens represent
Hi,
Has anyone seen any recent documentation on creating Windows 7 images
for OpenStack? I know it's supposed to be as easy as using kvm to
install it initially (as per the OpenStack docs) then importing that
image into glance, but there are some subtle things that I might be
missing because I hav
We (Rackspace) ended up acquiring a globally unique OUI for our public cloud,
but to be honest I don't believe most users will need to go down this road.
It's only really necessary if you expect to do L2VPNs to other clouds, both use
private mac ranges, and you expect them to overlap. Pretty l
On 10/19/2012 09:15 PM, 念远 wrote:
Hi,all!
In my ubuntu server (12.04.1), install openstack folsom, but i can't boot
instance,nova-compute.log display blow log !
who can help me,thanks!
2012-10-20 08:58:45 TRACE nova.compute.manager [instance:
d0a1c023-800c-4f1f-bb27-fb8279c6712e] File "/
I sent this to the openstack-dev list, and thought I'd double post this onto
the openstack list at Launchpad for additional feedback.
-joe
Begin forwarded message:
> From: heckj
> Subject: [openstack-dev] [keystone] Tokens representing authorization to
> projects/tenants in the Keystone V3 API
Sent from my iPad
On Oct 20, 2012, at 10:19, Salvatore Orlando wrote:
> I understand your concerns about conflicts with already assigned OUIs.
> It is however my opinion that it is not up to the Openstack Foundation, but
> to entities deploying Openstack, to buy MAC OUIs.
For comparison and
Hi Salvatore,
I agree with your suggestion that if we were all diligent and used locally
administered OUI then it is not an issue.
My concern now is that we are enabling pretty sophisticated tunneling
mechanism in Quantum (as you know being a Quantum key contributor), there
are more ways for the p
Monty mentioned this to me as well, and asked if its a cost the foundation
could pick up (should we all decide its the right thing to do).
I'm going to look into this question parallel while the discussion plays out
here.
On Oct 19, 2012, at 10:05 PM, Vinay Bannai wrote:
> I was talking t
If we purchase an OUI, is there a mechanism within Quantum to only allocate
Mac addresses with that prefix ?
Tim
From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
[mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Salvatore Orlando
Sent: 20 October 20
Hi Vinay,
I understand your concerns about conflicts with already assigned OUIs.
It is however my opinion that it is not up to the Openstack Foundation, but
to entities deploying Openstack, to buy MAC OUIs.
As regards Quantum, we should ensure the default MAC range we use is
locally assigned; unfo
13 matches
Mail list logo
