On 4/3/19 08:29, Thomas Goirand wrote:
On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
Hi list,
I've discovered the CloudStack datasource causes cloud-init to wait for 120 seconds
before continuing to the next datasource if no service is responding on port 80 on the
DHCP server address. As I am
On Thu, Apr 04, 2019 at 09:27:11AM +1300, Andrew Ruthven wrote:
> > > Would it be possible to move the Ec2 datasource up the list like "[
> > > NoCloud, AltCloud, ConfigDrive, OpenStack, Ec2, CloudStack,
> > > ${DIGITAL_OCEAN_SOURCE} MAAS, OVF, GCE, None ]"? This also seems to
> > > be in line
On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
> Hi list,
>
> I've discovered the CloudStack datasource causes cloud-init to wait for 120
> seconds before continuing to the next datasource if no service is responding
> on port 80 on the DHCP server address. As I am using an Ec2-style metadata
>
Greetings, We specialize in providing equity funding
for projects and corporate and Personal loan funding at 3% Interest Rate
for a duration of 10Years. We also have financial capability to provide
early stage funding including fresh cut BG's, MTN and MT760.
Kindly contact us as we will be
Hi list,
I've discovered the CloudStack datasource causes cloud-init to wait for 120
seconds before continuing to the next datasource if no service is responding on
port 80 on the DHCP server address. As I am using an Ec2-style metadata server,
I need to wait 120 seconds every time i boot an
