I think what you want is container ACLs for a given user (e.g using
devstack Kilo):
$ openrc user1 project1
$ swift post -r 'project2:user2' con1
$ swift stat con1
Account: AUTH_f399252f66574ea58ab465b3f8a4a2aa
Container: con1
Objects: 1
Bytes: 483
Read ACL: proj
So it will work!! great
I am running only single VM on single HOST. just doing some testing...
On Wed, Dec 16, 2015 at 4:54 PM, Chris Friesen
wrote:
> On 12/16/2015 03:17 PM, Satish Patel wrote:
>>
>> Hello,
>>
>> I am running openstack JUNO and created instance and later i did
>> manually set p
On 12/15/2015 12:23 PM, Satish Patel wrote:
If i enable "NUMATopologyFilter", Does JUNO support pinning?
FYI, i am following this link:
http://redhatstackblog.redhat.com/2015/05/05/cpu-pinning-and-numa-topology-awareness-in-openstack-compute/
Ah, sorry. I think that pinning only properly sup
On 12/16/2015 03:17 PM, Satish Patel wrote:
Hello,
I am running openstack JUNO and created instance and later i did
manually set pinning on compute node like following
virsh vcpupin instance-0053 0 0
virsh vcpupin instance-0053 1 1
Does it work? or we need to reboot instance etc?
Tha
Can we do this on JUNO? I badly need that?
On Wed, Dec 16, 2015 at 4:53 PM, Chris Friesen
wrote:
> On 12/15/2015 12:23 PM, Satish Patel wrote:
>>
>> If i enable "NUMATopologyFilter", Does JUNO support pinning?
>>
>> FYI, i am following this link:
>>
>> http://redhatstackblog.redhat.com/2015/05/0
Glad it helped
Thanks,
-js
-- Typo’s courtesy of Apple --
On December 16, 2015 at 1:19:59 PM, Satish Patel (satish@gmail.com) wrote:
Thanks jason!!
On Wed, Dec 16, 2015 at 11:57 AM, Jason Smith wrote:
> Hello,
>
> When booting an instance you can assign the IP with v4-fixed-ip=
Hello,
I am running openstack JUNO and created instance and later i did
manually set pinning on compute node like following
virsh vcpupin instance-0053 0 0
virsh vcpupin instance-0053 1 1
Does it work? or we need to reboot instance etc?
___
Ma
Thanks jason!!
On Wed, Dec 16, 2015 at 11:57 AM, Jason Smith wrote:
> Hello,
>
> When booting an instance you can assign the IP with v4-fixed-ip=
>
> Below is an example.
>
> $ nova boot --nic
> net-id=3ff9b903-e921-4752-a26f-cba8f1433992,v4-fixed-ip=10.0.0.30 \
> --image centos-6-cloud --key-n
Hey everybody!
The naming polls for N and O have started. You should have received an
email for each of them. They'll be open until the end of Dec 22 UTC.
Once there are presumptive winners in each, please remember that we will
then have the names vetted by the OpenStack Foundation's lawyers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey everyone!
I just released 2.2.0[1] of the kitchen-openstack driver. If your
curious the CHANGELOG is located here[2].
We're doing great work with kitchen-openstack, and would love to see
some more feedback on things the community would support
Thanks for your reply Matt. Your response about dhcp was helpful. The reason I
am considering DVR is that I am uncomfortable with the single point of failure
and bottleneck in the legacy scenario. But I am leaning toward the provider
scenario and am considering using the linux bridge.
Tyler
Fr
I suppose you assign ports which were previously setup for older vm.
On Dec 16, 2015 9:57 PM, "Satish Patel" wrote:
> Hello,
>
> does it possible assign IP when build VM? We have flat network setup
> with DHCP=false, but i have created start/end IP range so openstack
> assign IP when VM start.
>
Hello,
When booting an instance you can assign the IP with v4-fixed-ip=
Below is an example.
$ nova boot --nic
net-id=3ff9b903-e921-4752-a26f-cba8f1433992,v4-fixed-ip=10.0.0.30 \ --image
centos-6-cloud --key-name lars --flavor m1.small test0
Thanks,
-js
-- Typo’s courtesy of Apple --
Hello,
does it possible assign IP when build VM? We have flat network setup
with DHCP=false, but i have created start/end IP range so openstack
assign IP when VM start.
Yesterday one of my application crash and i was planing to rebuild VM
with new OS, but problem is how do i assign existing IP?
Hello,
I have installed Magnum with Liberty.
I have created a baymodel but I can't create a bay. The status is
CREATE_IN_PROGRESS and after a moment, the status of bay stack becomes
failed beacause of the time out.
I have pasted the magnum-conductor log :
http://paste.openstack.org/show/482051
Hi Parikshit,
Listing all tenants is not exposed in the publicUrl for Keystone v2.
Listing all tenants is a privileged operation, and that's the reason it is
only exposed in the admin endpoint.
If you switch to keystone v3, public and admin endpoint now exposes the
same capability. You should be
Hi All,
Listing tenants using adminURL lists all the tenants. Listing
the same from publicURL lists filtered list where token has access. Exposing
admin endpoint port is not recommended and is blocked from external network. Is
there a way to list all tenats in openstack using th
17 matches
Mail list logo