I asked one of our IT guys to look into this. He determined a port was in
the wrong VLAN and that's how my VM got an IP address from a different DHCP
server.
No CloudStack issue here. :)
Thanks
On Wed, Jan 22, 2014 at 11:05 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
That is an
blasted vlans and the trunks they rhode in on! :) glad all is well.
On Thu, Jan 23, 2014 at 10:45 AM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
I asked one of our IT guys to look into this. He determined a port was in
the wrong VLAN and that's how my VM got an IP address from a
+users
On 24-Jan-2014, at 2:38 AM, Ahmad Emneina aemne...@gmail.com wrote:
blasted vlans and the trunks they rhode in on! :) glad all is well.
On Thu, Jan 23, 2014 at 10:45 AM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
I asked one of our IT guys to look into this. He
Hi,
I was wondering if someone who deals with networking in CloudStack might
know something about this.
I have a development setup with one zone, one pod, and three clusters (one
VMware, one XenServer, and one KVM).
The IP addresses I've given to CloudStack span from 192.168.128.20 to
The IP address that CloudStack says is assigned to VM i-2-11-VM
(192.168.128.28) does not appear to be assigned to any VM in the system
(user or system VM).
On Wed, Jan 22, 2014 at 9:59 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
Hi,
I was wondering if someone who deals with
Slight correction (this may have been obvious from one of my screen shots):
The VM with the address outside of the range I gave to CloudStack is in a
XenServer cluster.
On Wed, Jan 22, 2014 at 10:03 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
The IP address that CloudStack says is
Hi Mike,
Can you please check the db table user_ip_address to see what are the ips
addresses are there.
IP will be picked from this table.
Thanks,
Jayapal
On 23-Jan-2014, at 10:35 AM, Mike Tutkowski mike.tutkow...@solidfire.com
wrote:
Slight correction (this may have been obvious from one
Hi Jayapal,
That table has 8 rows and includes IP addresses from 192.168.128.23 to
192.168.128.30 (which should be correct).
Thanks
On Wed, Jan 22, 2014 at 10:49 PM, Jayapal Reddy Uradi
jayapalreddy.ur...@citrix.com wrote:
Hi Mike,
Can you please check the db table user_ip_address to see
Mike, you might have another machine serving up DHCP on that network. If
thats the case get it to ignore cloudstack assigned mac addresses (06
prefix).
On Wed, Jan 22, 2014 at 9:53 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
Hi Jayapal,
That table has 8 rows and includes IP
That is an interesting possibility. Thanks, guys
On Wed, Jan 22, 2014 at 10:59 PM, Ahmad Emneina aemne...@gmail.com wrote:
Mike, you might have another machine serving up DHCP on that network. If
thats the case get it to ignore cloudstack assigned mac addresses (06
prefix).
On Wed, Jan
compromises due to time constraints.
I always intended to move the ip allocation into NetworkGurus and actually
attempted to several times but, at the end for various reasons, we just
couldn't complete that task. I generally believe that ip address allocation
can actually be done even
for various reasons,
we just couldn't complete that task. I generally believe that ip address
allocation can actually be done even without CloudStack's database, for
example, if it came from a master dhcp server or some IT central
database. So an interface like IpAddressReserver to abstract
infrastructure.) This would allow developing a plugin, if
needed that could provide in addition to NetworkElement and NetworkGuru
features the new External IP Address Allocation capability.
The points Alex made was to complete the work in the NetworkManager and
refactor out the IP Address
external providers. (The external
NetworkGuru also uses many of the same infrastructure.) This would allow
developing a plugin, if needed that could provide in addition to
NetworkElement and NetworkGuru features the new External IP Address
Allocation capability.
The points Alex made
]
Sent: Tuesday, August 06, 2013 2:29 PM
To: dev@cloudstack.apache.org
Subject: RE: IP Address Allocation
We can define a third type of element for IP Address Allocation, let me look
at the code and see is there is standard base class that it can extend or we
have to come up with a new base class
Agree that the IP Address allocation is different than the DHCP and DNS service
offered by the NetworkElements.
The third party NetworkGurus just reference the standard NetworkManager IP
Address Allocation routines, either directly (e.g.
_networkMgr.assignPublicIpAddress()) or by calling out
@cloudstack.apache.org
Subject: RE: IP Address Allocation
Can this be done on system VMs as well? I see that its targeted for the guests,
if there is a way to abstract and apply ip address on any component - it would
certainly make ACS much more flexible than it is now.
-Original Message
generally believe that ip address allocation
can actually be done even without CloudStack's database, for example, if it
came from a master dhcp server or some IT central database. So an interface
like IpAddressReserver to abstract that functionality would be great.
I have to say the number
Guru and element and let the guru do the IP address
allocation.
-Soheil
From: Soheil Eizadi [seiz...@infoblox.com]
Sent: Monday, August 05, 2013 2:35 PM
To: dev@cloudstack.apache.org
Subject: IP Address Allocation
I am trying to figure out what would
The NetworkGuru does a lot more than IP address allocation, e.g. handle the
Layer2/3 networking unique to the particular vendor. There are a lot of
NetworkElements providing their own NetworkGuru plugins (Nicira, MidoNet, ...)
extending the standard CloudStack Gurus.
The feature of providing
does a lot more than IP address allocation, e.g. handle
the Layer2/3 networking unique to the particular vendor. There are a lot
of NetworkElements providing their own NetworkGuru plugins (Nicira,
MidoNet, ...) extending the standard CloudStack Gurus.
The feature of providing IP Address Allocation
different
NetworkGurus may want to share the same ip address allocation tables/schemes so
an interface for them to share that code does make sense.
Note there's a difference between allocating ip address and the act of actually
issuing the ip address and associating the ip address to a fqdn
We can define a third type of element for IP Address Allocation, let me look at
the code and see is there is standard base class that it can extend or we have
to come up with a new base class like we have for NetworkElements.
-Soheil
From: Chiradeep
I am trying to figure out what would be the proper way for a Plugin to interact
with the CloudStack VM deployment and provide an authoritative IP Address from
its database versus the local CloudStack database. It looks like the
NetworkElements are not presented an opportunity to provide an IP
Address allocated that could be
reused.
Does anyone see a problem with this approach?
-Soheil
From: Soheil Eizadi [seiz...@infoblox.com]
Sent: Monday, August 05, 2013 2:35 PM
To: dev@cloudstack.apache.org
Subject: IP Address Allocation
I am trying to figure
25 matches
Mail list logo
