Hi
I am using Grizzly with Nova Network and VLAN.
I had creates 20 fixed range network with nova-manage network command.
1) Now I want to delete those all 20 networks, with single command not one
by one
2) There is no network type button in Openstack dashboard for managing nova
network, is it po
Hi
Thanks for your reply,
Yeh I had some misunderstand about Floating IPs.
Now is this possible I can create floating ip from dashboard/horizon?
Br.
Umar
On Sat, Feb 2, 2013 at 9:33 PM, Vishvananda Ishaya wrote:
>
> On Feb 1, 2013, at 8:24 PM, Umar Draz wrote:
>
> > So this
it.
>
> Vish
> On Feb 1, 2013 7:35 PM, "Umar Draz" wrote:
>
>> HI Vish,
>>
>> I always connect my Controller or Compute node with root user for nova
>> commands and here is the .bashrc of root user
>>
>> export OS_NO_CACHE=1
>>
3 at 6:27 AM, Vishvananda Ishaya wrote:
> What do you mean it isn't visible?
>
> you should be able to do:
>
> nova floating-ip-create mypool
>
> as any user.
>
> Vish
>
> On Feb 1, 2013, at 10:29 AM, Umar Draz wrote:
>
> Hi All,
>
> I have 3
Hi All,
I have 3 Tenant (admin, rebel, penguin). Also have 3 different users for
these Tenants
I have /25 network pool from my datacenter. I have created my default pool
using this name
nova-manage floating create --pool mypool --ip_range 73.63.93.128/25
Now the problem is I can only see this p
Hi Vish,
Yes, I did it assigned 45 ip address and then configured my HTTP load
balancer according to incoming domains.
Thanks Its work for me.
Best Regards,
Umar
On Thu, Jan 31, 2013 at 8:37 AM, Vishvananda Ishaya
wrote:
>
> On Jan 30, 2013, at 11:35 AM, Umar Draz wrote:
>
>
Hi Vish,
Assign direct/static IP address to Instance something like bridge rather
than nating is possible? Same like vSphare
Best Regards,
Umar
On Thu, Jan 31, 2013 at 8:37 AM, Vishvananda Ishaya
wrote:
>
> On Jan 30, 2013, at 11:35 AM, Umar Draz wrote:
>
> > Hi Caitlin,
est...@nexenta.com> wrote:
>
>
> Umar Draz asked:
>
> > I want to allocate multiple public ip address to instance, is this
> possible with openStack?
>
> In order to properly orchestrate resources you need to distinguish between
> the server holding that resource
> an
HI,
I want to alocate multiple public ip address to instance, is this possible
with openStack?
Best Regards,
Umar
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openst
~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
--
Umar Draz
Network Architect
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
hing.
> I'd like to reproduce your environment on my test system (it's not too
> distant from yours), so I can give you an accurate response.
> I'll keep you updated ASAP.
> Thanks for patience.
> Regards,
> Stefano
>
>
> On Tue, Jan 8, 2013 at 9:16 PM,
;ll be
> next step if we cannot find the problem this way)
>
> Do you have a standard iptables or do you have some custom rules? Also,
> what OS are the hypervisors running on?
> Thanks,
> Stefano
>
>
> On Tue, Jan 8, 2013 at 12:10 PM, Umar Draz wrote:
add a floating
> IP range and assign them to VMs.
> Hope this could solve the problem.
> Regards,
> Stefano
>
>
> On Mon, Jan 7, 2013 at 9:14 PM, Umar Draz wrote:
>
>> I did this on compute
>> root@compute1:~# echo 0 > /proc/sys/net/ipv4/conf/default/rp
ld solve the problem.
> Regards,
> Stefano
>
>
> On Mon, Jan 7, 2013 at 9:14 PM, Umar Draz wrote:
>
>> I did this on compute
>> root@compute1:~# echo 0 > /proc/sys/net/ipv4/conf/default/rp_filter
>>
>> and the result from vm
>> root@vm:~# ping
0? I needed to disable it today, otherwise
> I was facing problem similar to yours.
> Try to ping with rp_filter disabled, let's see if we can resolve the
> problem that way.
> Regards,
> Stefano
>
>
> On Mon, Jan 7, 2013 at 8:57 PM, Umar Draz wrote:
>
>>
ue, it
> seems a routing issue to me.
> Thanks,
> Stefano
>
>
> On Mon, Jan 7, 2013 at 7:38 PM, Umar Draz wrote:
>
>> I think My network configuration is ok,
>>
>> I can ping compute's own ip address 192.168.1.133 from virtual machine.
>> But I can
DHCP flat networking, maybe this page (and the
> chapter that contains it) could help:
>
> http://docs.openstack.org/essex/openstack-compute/admin/content/libvirt-flat-dhcp-networking.html
>
> Regards,
> Stefano
>
> On Mon, Jan 7, 2013 at 7:03 PM, Umar Draz wrote:
>
=nova.network.manager.FlatDHCPManager
force_dhcp_release=True
dhcpbridge_flagfile=/etc/nova/nova.conf
my_ip=6x.1x.84.132
public_interface=eth0
flat_network_bridge=br100
vlan_interface=eth1
flat_interface=eth1
fixed_range=10.0.0.0/24
Best Regards,
Umar
--
Umar Draz
Network Architect
e availability-zone parameter is
> ":"):
>
> nova boot --flavor 1 --image ubuntuRebel --availability-zone
> compute2:compute2 myInstanceName
>
> Thanks,
>
> Nate
>
>
> On Sun, Jan 6, 2013 at 4:39 PM, Umar Draz wrote:
>
>> Hi thanks For your awnswer
,
Umar
On Mon, Jan 7, 2013 at 1:46 AM, Anne Gentle wrote:
> Answers below.
>
> On Sun, Jan 6, 2013 at 12:22 PM, Umar Draz wrote:
>
>> Hi
>>
>> 1) How I can check which Release of Openstack I am using.
>>
>
> From
> http://docs.openstack.org/trunk/
t; Umar
> >
>
> Umar,
>
> The OpenStack user account that you are using to launch instances needs to
> have the admin role in keystone for the tenant you are operating within.
>
> See "add-user-role" in
> http://docs.openstack.org/trunk/openstack-c
gt;
> Nate
> On Jan 6, 2013 1:24 PM, "Umar Draz" wrote:
>
>> Hi
>>
>> 1) How I can check which Release of Openstack I am using.
>> 2) I want to boot instance on specific compute-node using this command
>> nova boot --image --flavor m1.tiny --key_
e nova:computenodename name of the instance. This command
> works fine in OpenStack ESSEX version.
>
> ** **
>
> Thanks
>
> Krishnaprasad
>
> *From:* openstack-bounces+narayana=uni-mainz...@lists.launchpad.net[mailto:
> openstack-bounces+narayana=uni-mainz...@lis
Hi
1) How I can check which Release of Openstack I am using.
2) I want to boot instance on specific compute-node using this command
nova boot --image --flavor m1.tiny --key_name mykey
--availability-zone nova:server2
but its not working. What is the correct way to do this?
Best Regards,
filtering traffic.
>
> Vish
>
>
> On Jan 3, 2013, at 10:25 AM, Umar Draz wrote:
>
> Hi Vish
>
> Here is the ifconfig output of *compute node*
>
> br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f
> inet addr:10.10.10.3 Bcast:10.10.10.255
s filtering traffic in the
> 10.10.10.0/24 range
>
> or
>
> c) br100 is not bridged into eth1
>
> (this would appear in brctl show which you didn't send)
>
>
> Vish
>
> On Jan 3, 2013, at 9:23 AM, Umar Draz wrote:
>
> Hi Vish
>
> Here is .
>
va.config look like? Specifically what is the setting
> for flat_interface?
>
> b) what command did you use to create your network?
>
> c) what is the output of brctl show?
>
> d) what is the output of ip addr show?
>
> Vish
>
> On Jan 2, 2013, at 11:11 PM, Umar Draz
ttp://notacash.com/,
> http://kharkivpy.org.ua/
>
>
> On Thu, Jan 3, 2013 at 9:11 AM, Umar Draz wrote:
>
>> Hi
>>
>> here is my setup
>>
>> 1) controller -> 63.73.22.22
>> 2) compute-1 - > 63.73.22.23
>> 3) compute-2 -> 63.73.22.24
Hi
here is my setup
1) controller -> 63.73.22.22
2) compute-1 - > 63.73.22.23
3) compute-2 -> 63.73.22.24
The Local network is 10.10.10.0/24 for virtual machines.
I have created 2 virtual machines. Controller automatically creates 1
Virtual machine on compute-1 and 2nd on compute-2.
1) Compute
29 matches
Mail list logo
