You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Stephan Seitz <s....@secretresearchfacility.com> on 2015/01/09 13:54:52 UTC
problem using own shared network offering
Hi all,
I'm trying to connect external, non-ACS hosts to particular VM's
(running in advanced Zone on 4.4.2).
What I've done:
- adding Hosts on a tagged VLAN at switch-layer
- creating a new "shared" guestnetwork w/ given VLAN id
Here a ran into trouble due to DHCP. One of that external hosts is (and
needs to be) a DHCP/TFTP. An ACS Router also answered to DHCP requests
which it shoudn't...
So i went further:
- deleting that new shared guestnetwork
- adding a "shared Network Without DHCP Service" NetworkOffering
- trying to create that new "shared" network w/ given VLAN id w/ my own
offering. <-- I'm unable to select other Offerings than the default
shared and "quickcloud".
I'm stuck here. Could someone please shed some light why I can't
introduce own shared NetworkOfferings?
Goal is:
That existing DHCP/TFTP should be able to kickstart baremetal hosts (as
it does since a while) and additionally particular ACS VM's on that
network.
Any tips really appreciated!
- Stephan
RE: problem using own shared network offering
Posted by Sanjeev Neelarapu <sa...@citrix.com>.
I think CS has never supported DHCP offering from external provider. Please correct me if I am wrong.
-Sanjeev
-----Original Message-----
From: Stephan Seitz [mailto:s.seitz@secretresearchfacility.com]
Sent: Monday, January 12, 2015 7:51 PM
To: users@cloudstack.apache.org
Subject: Re: problem using own shared network offering
Jayapal,
thank's for your quick response. Yes, I've tried to add the NetworkOffering via cloudmonkey / API but I sadly failed at the syntax for the serviceproviderlist (I'm not too deep into python)...
That are my two trials (without success since syntactical issues)
a) With DHCP directing to a BareMetalDhcpProvider
create networkoffering \
name=sharedExtDHCP \
availability=Optional \
conservemode=True \
displaytext=sharedExtDHCP \
egressdefaultpolicy=False \
guestiptype=Shared \
ispersistent=False \
networkrate=200 \
servicecapabilitylist=Dhcp,DNS,UserData \ serviceproviderlist=Dhcp:BaremetalDhcpProvider,DNS:VirtualRouter,UserData:VirtualRouter \ supportedservices=Dhcp,Dns,UserData \ traffictype=Guest
b) Without any DHCP
create networkoffering \
name=sharedNoDHCP \
availability=Optional \
conservemode=True \
displaytext=sharedNoDHCP \
egressdefaultpolicy=False \
guestiptype=Shared \
ispersistent=False \
networkrate=200 \
servicecapabilitylist=DNS,UserData \
serviceproviderlist=DNS:VirtualRouter,UserData:VirtualRouter \ supportedservices=Dns,UserData \ traffictype=Guest
Anyway, I'm curious about Sanjeev's response, stating that 4.4.2 doesn't support that kind of setup at all. Would this mean 4.3.x supports it and 4.4.x not? Or has it never supposed to work since?
Thanks!
- Stephan
Am Montag, den 12.01.2015, 05:39 +0000 schrieb Jayapal Reddy Uradi:
> Hi Stephan,
>
> Can you try the same creating shared network using the API
>
> Thanks,
> Jayapal
> On 12-Jan-2015, at 10:58 AM, Sanjeev Neelarapu
> <sa...@citrix.com>
> wrote:
>
> > Hi Stephan,
> >
> > ACS 4.4.2 does not support external DHCP server.
> >
> > -Sanjeev
> >
> > -----Original Message-----
> > From: Stephan Seitz [mailto:s.seitz@secretresearchfacility.com]
> > Sent: Friday, January 09, 2015 6:25 PM
> > To: users@cloudstack.apache.org
> > Subject: problem using own shared network offering
> >
> > Hi all,
> >
> > I'm trying to connect external, non-ACS hosts to particular VM's (running in advanced Zone on 4.4.2).
> > What I've done:
> > - adding Hosts on a tagged VLAN at switch-layer
> > - creating a new "shared" guestnetwork w/ given VLAN id Here a ran into trouble due to DHCP. One of that external hosts is (and needs to be) a DHCP/TFTP. An ACS Router also answered to DHCP requests which it shoudn't...
> > So i went further:
> > - deleting that new shared guestnetwork
> > - adding a "shared Network Without DHCP Service" NetworkOffering
> > - trying to create that new "shared" network w/ given VLAN id w/ my own offering. <-- I'm unable to select other Offerings than the default shared and "quickcloud".
> > I'm stuck here. Could someone please shed some light why I can't introduce own shared NetworkOfferings?
> >
> > Goal is:
> > That existing DHCP/TFTP should be able to kickstart baremetal hosts (as it does since a while) and additionally particular ACS VM's on that network.
> >
> > Any tips really appreciated!
> >
> > - Stephan
> >
> >
>
Re: problem using own shared network offering
Posted by Stephan Seitz <s....@secretresearchfacility.com>.
Jayapal,
thank's for your quick response. Yes, I've tried to add the
NetworkOffering via cloudmonkey / API but I sadly failed at the syntax
for the serviceproviderlist (I'm not too deep into python)...
That are my two trials (without success since syntactical issues)
a) With DHCP directing to a BareMetalDhcpProvider
create networkoffering \
name=sharedExtDHCP \
availability=Optional \
conservemode=True \
displaytext=sharedExtDHCP \
egressdefaultpolicy=False \
guestiptype=Shared \
ispersistent=False \
networkrate=200 \
servicecapabilitylist=Dhcp,DNS,UserData \
serviceproviderlist=Dhcp:BaremetalDhcpProvider,DNS:VirtualRouter,UserData:VirtualRouter \
supportedservices=Dhcp,Dns,UserData \
traffictype=Guest
b) Without any DHCP
create networkoffering \
name=sharedNoDHCP \
availability=Optional \
conservemode=True \
displaytext=sharedNoDHCP \
egressdefaultpolicy=False \
guestiptype=Shared \
ispersistent=False \
networkrate=200 \
servicecapabilitylist=DNS,UserData \
serviceproviderlist=DNS:VirtualRouter,UserData:VirtualRouter \
supportedservices=Dns,UserData \
traffictype=Guest
Anyway, I'm curious about Sanjeev's response, stating that 4.4.2 doesn't
support that kind of setup at all. Would this mean 4.3.x supports it and
4.4.x not? Or has it never supposed to work since?
Thanks!
- Stephan
Am Montag, den 12.01.2015, 05:39 +0000 schrieb Jayapal Reddy Uradi:
> Hi Stephan,
>
> Can you try the same creating shared network using the API
>
> Thanks,
> Jayapal
> On 12-Jan-2015, at 10:58 AM, Sanjeev Neelarapu <sa...@citrix.com>
> wrote:
>
> > Hi Stephan,
> >
> > ACS 4.4.2 does not support external DHCP server.
> >
> > -Sanjeev
> >
> > -----Original Message-----
> > From: Stephan Seitz [mailto:s.seitz@secretresearchfacility.com]
> > Sent: Friday, January 09, 2015 6:25 PM
> > To: users@cloudstack.apache.org
> > Subject: problem using own shared network offering
> >
> > Hi all,
> >
> > I'm trying to connect external, non-ACS hosts to particular VM's (running in advanced Zone on 4.4.2).
> > What I've done:
> > - adding Hosts on a tagged VLAN at switch-layer
> > - creating a new "shared" guestnetwork w/ given VLAN id Here a ran into trouble due to DHCP. One of that external hosts is (and needs to be) a DHCP/TFTP. An ACS Router also answered to DHCP requests which it shoudn't...
> > So i went further:
> > - deleting that new shared guestnetwork
> > - adding a "shared Network Without DHCP Service" NetworkOffering
> > - trying to create that new "shared" network w/ given VLAN id w/ my own offering. <-- I'm unable to select other Offerings than the default shared and "quickcloud".
> > I'm stuck here. Could someone please shed some light why I can't introduce own shared NetworkOfferings?
> >
> > Goal is:
> > That existing DHCP/TFTP should be able to kickstart baremetal hosts (as it does since a while) and additionally particular ACS VM's on that network.
> >
> > Any tips really appreciated!
> >
> > - Stephan
> >
> >
>
Re: problem using own shared network offering
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
Hi Stephan,
Can you try the same creating shared network using the API
Thanks,
Jayapal
On 12-Jan-2015, at 10:58 AM, Sanjeev Neelarapu <sa...@citrix.com>
wrote:
> Hi Stephan,
>
> ACS 4.4.2 does not support external DHCP server.
>
> -Sanjeev
>
> -----Original Message-----
> From: Stephan Seitz [mailto:s.seitz@secretresearchfacility.com]
> Sent: Friday, January 09, 2015 6:25 PM
> To: users@cloudstack.apache.org
> Subject: problem using own shared network offering
>
> Hi all,
>
> I'm trying to connect external, non-ACS hosts to particular VM's (running in advanced Zone on 4.4.2).
> What I've done:
> - adding Hosts on a tagged VLAN at switch-layer
> - creating a new "shared" guestnetwork w/ given VLAN id Here a ran into trouble due to DHCP. One of that external hosts is (and needs to be) a DHCP/TFTP. An ACS Router also answered to DHCP requests which it shoudn't...
> So i went further:
> - deleting that new shared guestnetwork
> - adding a "shared Network Without DHCP Service" NetworkOffering
> - trying to create that new "shared" network w/ given VLAN id w/ my own offering. <-- I'm unable to select other Offerings than the default shared and "quickcloud".
> I'm stuck here. Could someone please shed some light why I can't introduce own shared NetworkOfferings?
>
> Goal is:
> That existing DHCP/TFTP should be able to kickstart baremetal hosts (as it does since a while) and additionally particular ACS VM's on that network.
>
> Any tips really appreciated!
>
> - Stephan
>
>
RE: problem using own shared network offering
Posted by Sanjeev Neelarapu <sa...@citrix.com>.
Hi Stephan,
ACS 4.4.2 does not support external DHCP server.
-Sanjeev
-----Original Message-----
From: Stephan Seitz [mailto:s.seitz@secretresearchfacility.com]
Sent: Friday, January 09, 2015 6:25 PM
To: users@cloudstack.apache.org
Subject: problem using own shared network offering
Hi all,
I'm trying to connect external, non-ACS hosts to particular VM's (running in advanced Zone on 4.4.2).
What I've done:
- adding Hosts on a tagged VLAN at switch-layer
- creating a new "shared" guestnetwork w/ given VLAN id Here a ran into trouble due to DHCP. One of that external hosts is (and needs to be) a DHCP/TFTP. An ACS Router also answered to DHCP requests which it shoudn't...
So i went further:
- deleting that new shared guestnetwork
- adding a "shared Network Without DHCP Service" NetworkOffering
- trying to create that new "shared" network w/ given VLAN id w/ my own offering. <-- I'm unable to select other Offerings than the default shared and "quickcloud".
I'm stuck here. Could someone please shed some light why I can't introduce own shared NetworkOfferings?
Goal is:
That existing DHCP/TFTP should be able to kickstart baremetal hosts (as it does since a while) and additionally particular ACS VM's on that network.
Any tips really appreciated!
- Stephan