Specifying boot-resource for MaaS API Deploy


up vote
0
down vote
favorite
I want to deploy a machine via the API at /machines/system_id/?op=deploy
. I would have expected this to take boot-resource ID as parameter, but instead it takes distro_series
and hwe_kernel
.
So I fetch the information about the boot-resource from /boot-resources/id/
. It gives me 'name', which looks like "<os>/<series>"
.
Making the API call with either POST body distro_series="<distro>"
or distro_series="<os>/<series>"
just causes the deployment to go through with the default Xenial.
This is also the case for custom, non-linux images (with either "win2012r2"
or "windows/win2012r2"
).
I'm using MaaS version 2.3.0.
Any help at all would be appreciated.
maas
add a comment |Â
up vote
0
down vote
favorite
I want to deploy a machine via the API at /machines/system_id/?op=deploy
. I would have expected this to take boot-resource ID as parameter, but instead it takes distro_series
and hwe_kernel
.
So I fetch the information about the boot-resource from /boot-resources/id/
. It gives me 'name', which looks like "<os>/<series>"
.
Making the API call with either POST body distro_series="<distro>"
or distro_series="<os>/<series>"
just causes the deployment to go through with the default Xenial.
This is also the case for custom, non-linux images (with either "win2012r2"
or "windows/win2012r2"
).
I'm using MaaS version 2.3.0.
Any help at all would be appreciated.
maas
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to deploy a machine via the API at /machines/system_id/?op=deploy
. I would have expected this to take boot-resource ID as parameter, but instead it takes distro_series
and hwe_kernel
.
So I fetch the information about the boot-resource from /boot-resources/id/
. It gives me 'name', which looks like "<os>/<series>"
.
Making the API call with either POST body distro_series="<distro>"
or distro_series="<os>/<series>"
just causes the deployment to go through with the default Xenial.
This is also the case for custom, non-linux images (with either "win2012r2"
or "windows/win2012r2"
).
I'm using MaaS version 2.3.0.
Any help at all would be appreciated.
maas
I want to deploy a machine via the API at /machines/system_id/?op=deploy
. I would have expected this to take boot-resource ID as parameter, but instead it takes distro_series
and hwe_kernel
.
So I fetch the information about the boot-resource from /boot-resources/id/
. It gives me 'name', which looks like "<os>/<series>"
.
Making the API call with either POST body distro_series="<distro>"
or distro_series="<os>/<series>"
just causes the deployment to go through with the default Xenial.
This is also the case for custom, non-linux images (with either "win2012r2"
or "windows/win2012r2"
).
I'm using MaaS version 2.3.0.
Any help at all would be appreciated.
maas
maas
edited Mar 10 at 0:09
asked Mar 9 at 11:16
Allan
13
13
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1013371%2fspecifying-boot-resource-for-maas-api-deploy%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