What is the most authoritative file/process for managing IP addresses on an 18.04 server?
Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
edited May 23 at 12:46
Melebius
3,66041636
asked May 14 at 20:20
kartik_subbarao
1267
add a comment |Â
up vote
3
down vote
favorite
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
edited May 23 at 12:46
Melebius
3,66041636
asked May 14 at 20:20
kartik_subbarao
1267
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 at 15:18
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
edited May 23 at 12:46
Melebius
3,66041636
asked May 14 at 20:20
kartik_subbarao
1267
The 18.04 server installation process creates /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, which, in turn, seems to generate /etc/netplan/50-cloud-init.yaml. I can't seem to find exactly how 50-cloud-init.yaml gets generated from 50-curtin-networking.cfg though.
What is the recommended way to manage IP addresses on an 18.04 server? Edit 50-curtin-networking.cfg, and then run some command (?) to update 50-cloud-init.yaml? Or some other process?
networking 18.04 ip-address netplan cloud-init
edited May 23 at 12:46
Melebius
3,66041636
asked May 14 at 20:20
kartik_subbarao
1267
edited May 23 at 12:46
Melebius
3,66041636
edited May 23 at 12:46
Melebius
3,66041636
edited May 23 at 12:46
Melebius
3,66041636
3,66041636
asked May 14 at 20:20
kartik_subbarao
1267
asked May 14 at 20:20
kartik_subbarao
1267
asked May 14 at 20:20
kartik_subbarao
1267
1267
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 at 15:18
add a comment |Â
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.
– Rinzwind
May 23 at 14:00
I don't have any files named50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?
– kartik_subbarao
May 23 at 15:18
network-config generates 50-cloud-init.cfg. and cloud-init ( cloudinit.readthedocs.io/en/latest ) triggers network-config ( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 at 14:00
network-config generates 50-cloud-init.cfg. and cloud-init ( cloudinit.readthedocs.io/en/latest ) triggers network-config ( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 at 14:00
I don't have any files named
50-cloud-init.cfg -- I have 50-curtin-networking.cfg and 50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate 50-cloud-init.yaml from 50-curtin-networking.cfg?– kartik_subbarao
May 23 at 15:18
I don't have any files named
50-cloud-init.cfg -- I have 50-curtin-networking.cfg and 50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate 50-cloud-init.yaml from 50-curtin-networking.cfg?– kartik_subbarao
May 23 at 15:18
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 at 20:36
chili555
36.3k54776
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
 |Â
show 1 more comment
up vote
0
down vote
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
answered Aug 6 at 15:57
JargonMan
11
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 at 20:36
chili555
36.3k54776
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
 |Â
show 1 more comment
up vote
0
down vote
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 at 20:36
chili555
36.3k54776
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
 |Â
show 1 more comment
up vote
0
down vote
up vote
0
down vote
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 at 20:36
chili555
36.3k54776
I assume this is an ordinary server, behind a router or switch that then connects to the internet. I'd rename the 50-cloud-init.yaml file:
sudo mv /etc/netplan/50-cloud-init.yaml /etc/netplan/01-netcfg.yaml
Then find out the relevant interface name:
ifconfig
Assuming, for an example, that your relevant interface is enp0s25, edit the file:
sudo nano /etc/netplan/01-netcfg.yaml
Amend the file to read:
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: no
addresses: [192.168.100.40/22]
gateway4: 192.168.100.1
nameservers:
addresses: [8.8.8.8,8.8.4.4]
Of course, susbstitue your exact details here. Spacing, indentation, etc. are crucial. Proofread carefully. Save (Ctrl+o followed by Enter) and close (Ctrl+x) the text editor.
Next:
sudo netplan apply
sudo ip link set enp0s25 down
sudo ip link set enp0s25 up
Did you get the requested IP address?
ip addr show
Can you ping?
ping -c3 8.8.8.8
ping -c3 www.ubuntu.com
If you get ping returns, you are all set.
answered May 14 at 20:36
chili555
36.3k54776
answered May 14 at 20:36
chili555
36.3k54776
answered May 14 at 20:36
chili555
36.3k54776
answered May 14 at 20:36
chili555
36.3k54776
36.3k54776
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
 |Â
show 1 more comment
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
It seems like you're suggesting that the text at the top of 50-cloud-init.yaml, warning against editing it manually, should be ignored :-) This may end up being the approach taken, but I'd ideally like to understand why that text is there in the first place. Presumably the designers had some workflow in mind when they created that process. And what about /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg?
– kartik_subbarao
May 14 at 21:01
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
I've renamed the question to hopefully make it clearer.
– kartik_subbarao
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
Is this a cloud instance?
– chili555
May 14 at 21:16
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
No, it is not a cloud instance. It is a standalone server on an internal network.
– kartik_subbarao
May 15 at 12:20
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
That's what I meant above when I said, "I assume this is an ordinary server, ..." Please check here: blog.printk.io/2018/04/… I still think 01-netcfg.yaml is appropriate.
– chili555
May 15 at 13:03
 |Â
show 1 more comment
up vote
0
down vote
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
answered Aug 6 at 15:57
JargonMan
11
add a comment |Â
up vote
0
down vote
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
answered Aug 6 at 15:57
JargonMan
11
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
answered Aug 6 at 15:57
JargonMan
11
Make your networking changes to the /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg file as if you were putting them in the yaml file.
Then do the following:
sudo cloud-init clean
sudo cloud-init init
sudo netplan apply
This will process your 50-curtin-networking.cfg file, generate the 50-cloud-init.yaml file and apply the yaml file netplan configuration.
In this way, you can write your networking config in the 50-curtin-networking.cfg file as the comments imply you should do.
A lot of the confusion between setting networking up in the 50-cloud-init.yaml file vs the 01-netcfg.yaml found in the /etc/netplan directory comes down to the installer used for Ubuntu 18.04 LTS.
The live installer uses cloud-init, whereas the alternate installer does not.
So for networking your installer choice changes how you will set up networking.
ubuntu-18.04.1-server-amd64.iso -> 01-netcfg.yaml
ubuntu-18.04.1-live-server-amd64.iso -> 50-curtin-networking.cfg
answered Aug 6 at 15:57
JargonMan
11
edited Aug 13 at 13:20
answered Aug 6 at 15:57
JargonMan
11
answered Aug 6 at 15:57
JargonMan
11
answered Aug 6 at 15:57
JargonMan
11
11
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036266%2fwhat-is-the-most-authoritative-file-process-for-managing-ip-addresses-on-an-18-0%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
network-configgenerates50-cloud-init.cfg. andcloud-init( cloudinit.readthedocs.io/en/latest ) triggersnetwork-config( cloudinit.readthedocs.io/en/latest/topics/network-config.html ). That happens on initial creation, and on restarting but only when your force it.– Rinzwind
May 23 at 14:00
I don't have any files named
50-cloud-init.cfg-- I have50-curtin-networking.cfgand50-cloud-init-yaml. Did you mean the former? If so, how exactly do you "force" cloud-init to regenerate50-cloud-init.yamlfrom50-curtin-networking.cfg?– kartik_subbarao
May 23 at 15:18