Hi, I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any. Thanks, Curtis
On 12/20/2018 07:12 AM, Curtis wrote:
Hi,
I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site, powered on, and immediately register itself with either a local inventory management system or a remote one? In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing that *responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the team that handles hardware inventory. I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are pretty slim, IMHO. Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles base hardware provisioning and I'm definitely interested in seeing if other shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!). Best, -jay [1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits I suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme differences in OEM vendor support will rule out a generic workable solution here as many in the Ironic community will likely attest to [3]. If you can rely on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however. [2] https://www.redhat.com/en/technologies/management/satellite [3] https://github.com/openstack/ironic/tree/master/ironic/drivers
I'm also very interested in the use case here, for accelerators deployed at edge it would be needed to have zero touch provision capability as Jay described. I'm wondering if the open firmware project [0] could be of help here by any means ? I saw there was a FB presentation that they use it for provisioning automation in their datacenter at the OCP Regional Summit. [0] https://www.opencompute.org/wiki/Open_System_Firmware On Thu, Dec 20, 2018 at 9:09 PM Jay Pipes <jaypipes@gmail.com> wrote:
On 12/20/2018 07:12 AM, Curtis wrote:
Hi,
I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site, powered on, and immediately register itself with either a local inventory management system or a remote one?
In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing that *responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the team that handles hardware inventory.
I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are pretty slim, IMHO.
Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles base hardware provisioning and I'm definitely interested in seeing if other shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!).
Best, -jay
[1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits I suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme differences in OEM vendor support will rule out a generic workable solution here as many in the Ironic community will likely attest to [3]. If you can rely on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however.
[2] https://www.redhat.com/en/technologies/management/satellite
[3] https://github.com/openstack/ironic/tree/master/ironic/drivers
-- Zhipeng (Howard) Huang Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen
On Thu, Dec 20, 2018 at 8:22 AM Zhipeng Huang <zhipengh512@gmail.com> wrote:
I'm also very interested in the use case here, for accelerators deployed at edge it would be needed to have zero touch provision capability as Jay described.
Accelerators...interesting. I would be happy to hear more about that use case.
I'm wondering if the open firmware project [0] could be of help here by any means ? I saw there was a FB presentation that they use it for provisioning automation in their datacenter at the OCP Regional Summit.
Quite possibly, or perhaps ONIE as well, or a combination. :) Mostly I was wondering if there had been any discussion in the edge group, or if anyone knows of any major activities around this area. I think a zero touch related group was just recently started at ETSI [1] but haven't read through related docs yet. Thanks, Curtis [1]: https://www.etsi.org/index.php/technologies-clusters/technologies/zero-touch...
On Thu, Dec 20, 2018 at 9:09 PM Jay Pipes <jaypipes@gmail.com> wrote:
On 12/20/2018 07:12 AM, Curtis wrote:
Hi,
I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site, powered on, and immediately register itself with either a local inventory management system or a remote one?
In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing that *responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the team that handles hardware inventory.
I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are pretty slim, IMHO.
Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles base hardware provisioning and I'm definitely interested in seeing if other shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!).
Best, -jay
[1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits I suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme differences in OEM vendor support will rule out a generic workable solution here as many in the Ironic community will likely attest to [3]. If you can rely on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however.
[2] https://www.redhat.com/en/technologies/management/satellite
[3] https://github.com/openstack/ironic/tree/master/ironic/drivers
-- Zhipeng (Howard) Huang
Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen
-- Blog: serverascode.com
On Thu, Dec 20, 2018 at 8:09 AM Jay Pipes <jaypipes@gmail.com> wrote:
On 12/20/2018 07:12 AM, Curtis wrote:
Hi,
I've been looking through the docs I can find related to the edge working group, and I'm wondering if there has been any discussion/documentation of a Zero Touch Provisioning use case. I can't seem to find anything, but I may not be looking in the right place. Just wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site, powered on, and immediately register itself with either a local inventory management system or a remote one?
In this case, yes that is what I'm talking about, just the provisioning aspect, and mostly related to the "edge" which in my case I usually consider to be one or two physical servers (but that's just one use case). I'm a relatively new member of the StarlingX TSC and there is some discussion about deployment models, of which ZTP would presumably be a part, so I wanted to check in with the edge working group to see what's been going on in that area if anything.
In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing that *responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the team that handles hardware inventory.
I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are pretty slim, IMHO.
Well, perhaps ONIE [1] is the best example. Switches that can run multiple network OSes have pretty much standardized on it. But I don't know if ONIE is the right example here, though it very well might be.
Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles base hardware provisioning and I'm definitely interested in seeing if other shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!).
Best, -jay
[1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits I suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme differences in OEM vendor support will rule out a generic workable solution here as many in the Ironic community will likely attest to [3]. If you can rely on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however.
[2] https://www.redhat.com/en/technologies/management/satellite
[3] https://github.com/openstack/ironic/tree/master/ironic/drivers
[1]: https://opencomputeproject.github.io/onie/ -- Blog: serverascode.com
On 12/20/2018 08:47 AM, Curtis wrote:
On Thu, Dec 20, 2018 at 8:09 AM Jay Pipes <jaypipes@gmail.com <mailto:jaypipes@gmail.com>> wrote:
On 12/20/2018 07:12 AM, Curtis wrote: > Hi, > > I've been looking through the docs I can find related to the edge > working group, and I'm wondering if there has been any > discussion/documentation of a Zero Touch Provisioning use case. I can't > seem to find anything, but I may not be looking in the right place. Just > wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site, powered on, and immediately register itself with either a local inventory management system or a remote one?
In this case, yes that is what I'm talking about, just the provisioning aspect, and mostly related to the "edge" which in my case I usually consider to be one or two physical servers (but that's just one use case).
I'm a relatively new member of the StarlingX TSC and there is some discussion about deployment models, of which ZTP would presumably be a part, so I wanted to check in with the edge working group to see what's been going on in that area if anything.
I'm not involved in StarlingX so can't speak to that area.
In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing that *responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the team that handles hardware inventory.
I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are pretty slim, IMHO.
Well, perhaps ONIE [1] is the best example. Switches that can run multiple network OSes have pretty much standardized on it. But I don't know if ONIE is the right example here, though it very well might be.
ONIE looks interesting, thanks for the link. It does seem to be specific to network switches, though, not general compute hardware (or servers that need large root disks and partitioning). It seems to be kind of a custom TFTP server for network devices? Is ONIE something you're saying would be a solution for inventory management? Because I don't really see anything in there (or the scope of ONIE) about that... Best, -jay
Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles base hardware provisioning and I'm definitely interested in seeing if other shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!).
Best, -jay
[1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits I suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme differences in OEM vendor support will rule out a generic workable solution here as many in the Ironic community will likely attest to [3]. If you can rely on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however.
[2] https://www.redhat.com/en/technologies/management/satellite
[3] https://github.com/openstack/ironic/tree/master/ironic/drivers
[1]: https://opencomputeproject.github.io/onie/
-- Blog: serverascode.com <http://serverascode.com>
On Thu, Dec 20, 2018 at 9:01 AM Jay Pipes <jaypipes@gmail.com> wrote:
On Thu, Dec 20, 2018 at 8:09 AM Jay Pipes <jaypipes@gmail.com <mailto:jaypipes@gmail.com>> wrote:
On 12/20/2018 07:12 AM, Curtis wrote: > Hi, > > I've been looking through the docs I can find related to the edge > working group, and I'm wondering if there has been any > discussion/documentation of a Zero Touch Provisioning use case. I can't > seem to find anything, but I may not be looking in the right place. Just > wanted to double check and see what the current state is, if any.
I take it that by "zero touch *provisioning*" (emphasis added to differentiate from zero *configuration* networking, you are referring to the ability for a new server to be rack-and-stacked in a site,
On 12/20/2018 08:47 AM, Curtis wrote: powered
on, and immediately register itself with either a local inventory management system or a remote one?
In this case, yes that is what I'm talking about, just the provisioning aspect, and mostly related to the "edge" which in my case I usually consider to be one or two physical servers (but that's just one use
case).
I'm a relatively new member of the StarlingX TSC and there is some discussion about deployment models, of which ZTP would presumably be a part, so I wanted to check in with the edge working group to see what's been going on in that area if anything.
I'm not involved in StarlingX so can't speak to that area.
In either case, the issue I foresee is that the firmware (or initial boot/ramdisk that comes from the factory or supply chain team) will need to have some program installed in it that sends out a request looking for some known/assumed inventory management service [1]. The thing
that
*responds* to such a request would, of course, need to be already installed and available either on a switch or a pre-installed machine pingable on the out-of-band network and already configured by the
team
that handles hardware inventory.
I can see some vendors working on their own custom low-touch provisioning software -- and this software would likely end up depending on their own proprietary (or subscription-based) server software ala Red Hat's Satellite software [2]). But getting all the vendors to come together on a unified low-touch provisioning system? Chances are
pretty
slim, IMHO.
Well, perhaps ONIE [1] is the best example. Switches that can run multiple network OSes have pretty much standardized on it. But I don't know if ONIE is the right example here, though it very well might be.
ONIE looks interesting, thanks for the link. It does seem to be specific to network switches, though, not general compute hardware (or servers that need large root disks and partitioning). It seems to be kind of a custom TFTP server for network devices?
Is ONIE something you're saying would be a solution for inventory management? Because I don't really see anything in there (or the scope of ONIE) about that...
No, it doesn't do inventory management. It's like a small base OS for network switches, they come with it, boot up into it, and you can use it to install other OSes. At least that's how it's used with the whitebox switches I have. With ONIE it'd install the OS, then the initial OS could register with some kind of inventory system. Thanks, Curtis
Best, -jay
Still, it's an interesting problem domain and I'd be interested in sharing thoughts and discussing it with others. Here at "Yahoo!/Oath/Verizon Media Group/Whatever we'll be called next month" we have custom software (and a bit of custom hardware!) that handles
base
hardware provisioning and I'm definitely interested in seeing if
other
shops that handle hundreds of thousands of baremetal machines are looking to collaborate in this area ("edge" or otherwise!).
Best, -jay
[1] this could be done via some custom DHCPDISCOVER/DHCPREQUEST bits
I
suppose -- which would require a DHCP client in the firmware/bootdisk -- but more likely would depend on the IPMI/BMC system in use for the hardware. As soon as IPMI/BMC comes into play, the extreme
differences
in OEM vendor support will rule out a generic workable solution here
as
many in the Ironic community will likely attest to [3]. If you can
rely
on a homogeneous set of hardware at edge sites, you might be able to put something together that just suits your company's need, however.
[2] https://www.redhat.com/en/technologies/management/satellite
[3] https://github.com/openstack/ironic/tree/master/ironic/drivers
[1]: https://opencomputeproject.github.io/onie/
-- Blog: serverascode.com <http://serverascode.com>
-- Blog: serverascode.com
On 12/20/2018 09:33 AM, Curtis wrote:
No, it doesn't do inventory management. It's like a small base OS for network switches, they come with it, boot up into it, and you can use it to install other OSes. At least that's how it's used with the whitebox switches I have. With ONIE it'd install the OS, then the initial OS could register with some kind of inventory system.
What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :) Best, -jay
On Thu, Dec 20, 2018 at 9:35 AM Jay Pipes <jaypipes@gmail.com> wrote:
On 12/20/2018 09:33 AM, Curtis wrote:
No, it doesn't do inventory management. It's like a small base OS for network switches, they come with it, boot up into it, and you can use it to install other OSes. At least that's how it's used with the whitebox switches I have. With ONIE it'd install the OS, then the initial OS could register with some kind of inventory system.
What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :)
I'm not sure; that's a good question. I was just using it as an example of a piece of ZTP related technology that has been adopted by vendors who build physical devices and include them by default, though of course, only a subset of network switches. :) If ONIE was a good example, and it could not be used for general compute hardware, then perhaps something like it could be built using lessons learned by ONIE. I dunno. :) Thanks, Curits
Best, -jay
-- Blog: serverascode.com
ICYMI: https://blog.ipspace.net/2018/12/zero-touch-provisioning-with-patrick_20.htm... Shall we collect items of OCP/OpenStack components that could composite a ZTP stack somewhere ? On Thu, Dec 20, 2018 at 10:51 PM Curtis <serverascode@gmail.com> wrote:
On Thu, Dec 20, 2018 at 9:35 AM Jay Pipes <jaypipes@gmail.com> wrote:
On 12/20/2018 09:33 AM, Curtis wrote:
No, it doesn't do inventory management. It's like a small base OS for network switches, they come with it, boot up into it, and you can use it to install other OSes. At least that's how it's used with the whitebox switches I have. With ONIE it'd install the OS, then the initial OS could register with some kind of inventory system.
What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :)
I'm not sure; that's a good question. I was just using it as an example of a piece of ZTP related technology that has been adopted by vendors who build physical devices and include them by default, though of course, only a subset of network switches. :)
If ONIE was a good example, and it could not be used for general compute hardware, then perhaps something like it could be built using lessons learned by ONIE. I dunno. :)
Thanks, Curits
Best, -jay
-- Blog: serverascode.com
-- Zhipeng (Howard) Huang Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen
On 12/21/2018 01:40 AM, Zhipeng Huang wrote:
ICYMI: https://blog.ipspace.net/2018/12/zero-touch-provisioning-with-patrick_20.htm...
From that article: "ZTP can be used internally connecting to an internal provisioning server, and it can be used externally connecting to an external provisioning server. Some commercial products use ZTP in connection with a vendor-controlled cloud-based provisioning server." Funny, that's almost exactly what I said in my original response on this thread :)
Shall we collect items of OCP/OpenStack components that could composite a ZTP stack somewhere ?
Sure, just make sure we're being explicit about the things we're discussing. If you want to focus exclusively on *network device* provisioning, that's fine, but that should be explicitly stated. Network device provisioning is an important but ultimately tiny part of infrastructure provisioning. Unfortunately, most of the telco and network OEM community (understandably) only refer to network device provisioning when they talk about "ZTP". Also, the less this can be pidgeon-holed into the amorphous "edge" category, the better, IMHO ;) Best, -jay
On Thu, Dec 20, 2018 at 10:51 PM Curtis <serverascode@gmail.com <mailto:serverascode@gmail.com>> wrote:
On Thu, Dec 20, 2018 at 9:35 AM Jay Pipes <jaypipes@gmail.com <mailto:jaypipes@gmail.com>> wrote:
On 12/20/2018 09:33 AM, Curtis wrote: > No, it doesn't do inventory management. It's like a small base OS for > network switches, they come with it, boot up into it, and you can use it > to install other OSes. At least that's how it's used with the whitebox > switches I have. With ONIE it'd install the OS, then the initial OS > could register with some kind of inventory system.
What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :)
I'm not sure; that's a good question. I was just using it as an example of a piece of ZTP related technology that has been adopted by vendors who build physical devices and include them by default, though of course, only a subset of network switches. :)
If ONIE was a good example, and it could not be used for general compute hardware, then perhaps something like it could be built using lessons learned by ONIE. I dunno. :)
Thanks, Curits
Best, -jay
-- Blog: serverascode.com <http://serverascode.com>
-- Zhipeng (Howard) Huang
Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com <mailto:huangzhipeng@huawei.com> Office: Huawei Industrial Base, Longgang, Shenzhen
Hi, Apologies, I’ve just got to this thread. I don’t remember discussing this topic in details with the Edge group yet. ZTP came up as a desire, but we didn’t get to the point of going into details on what it means until now. I think it would be great to capture the discussion on this thread as well as further aspects for consideration on the Edge Computing Group wiki and use it as a central place for StarlingX and relevant OpenStack projects such as Cyborg to benefit from as input for their work. I added it to the agenda for the Edge group weekly call[1] for tomorrow to bring it up as a discussion point and can keep it there if we have people around interested in discussing it further. Thanks, Ildikó [1] https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings
On 2018. Dec 21., at 6:25, Jay Pipes <jaypipes@gmail.com> wrote:
On 12/21/2018 01:40 AM, Zhipeng Huang wrote:
ICYMI: https://blog.ipspace.net/2018/12/zero-touch-provisioning-with-patrick_20.htm...
From that article:
"ZTP can be used internally connecting to an internal provisioning server, and it can be used externally connecting to an external provisioning server. Some commercial products use ZTP in connection with a vendor-controlled cloud-based provisioning server."
Funny, that's almost exactly what I said in my original response on this thread :)
Shall we collect items of OCP/OpenStack components that could composite a ZTP stack somewhere ?
Sure, just make sure we're being explicit about the things we're discussing. If you want to focus exclusively on *network device* provisioning, that's fine, but that should be explicitly stated.
Network device provisioning is an important but ultimately tiny part of infrastructure provisioning. Unfortunately, most of the telco and network OEM community (understandably) only refer to network device provisioning when they talk about "ZTP".
Also, the less this can be pidgeon-holed into the amorphous "edge" category, the better, IMHO ;)
Best, -jay
On Thu, Dec 20, 2018 at 10:51 PM Curtis <serverascode@gmail.com <mailto:serverascode@gmail.com>> wrote: On Thu, Dec 20, 2018 at 9:35 AM Jay Pipes <jaypipes@gmail.com <mailto:jaypipes@gmail.com>> wrote: On 12/20/2018 09:33 AM, Curtis wrote: > No, it doesn't do inventory management. It's like a small base OS for > network switches, they come with it, boot up into it, and you can use it > to install other OSes. At least that's how it's used with the whitebox > switches I have. With ONIE it'd install the OS, then the initial OS > could register with some kind of inventory system. What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :) I'm not sure; that's a good question. I was just using it as an example of a piece of ZTP related technology that has been adopted by vendors who build physical devices and include them by default, though of course, only a subset of network switches. :) If ONIE was a good example, and it could not be used for general compute hardware, then perhaps something like it could be built using lessons learned by ONIE. I dunno. :) Thanks, Curits Best, -jay -- Blog: serverascode.com <http://serverascode.com> -- Zhipeng (Howard) Huang Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com <mailto:huangzhipeng@huawei.com> Office: Huawei Industrial Base, Longgang, Shenzhen
Thanks Ildiko ! :) On Tue, Jan 15, 2019 at 10:12 AM Ildiko Vancsa <ildiko.vancsa@gmail.com> wrote:
Hi,
Apologies, I’ve just got to this thread.
I don’t remember discussing this topic in details with the Edge group yet. ZTP came up as a desire, but we didn’t get to the point of going into details on what it means until now.
I think it would be great to capture the discussion on this thread as well as further aspects for consideration on the Edge Computing Group wiki and use it as a central place for StarlingX and relevant OpenStack projects such as Cyborg to benefit from as input for their work.
I added it to the agenda for the Edge group weekly call[1] for tomorrow to bring it up as a discussion point and can keep it there if we have people around interested in discussing it further.
Thanks, Ildikó
[1] https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings
On 2018. Dec 21., at 6:25, Jay Pipes <jaypipes@gmail.com> wrote:
On 12/21/2018 01:40 AM, Zhipeng Huang wrote:
ICYMI: https://blog.ipspace.net/2018/12/zero-touch-provisioning-with-patrick_20.htm...
From that article:
"ZTP can be used internally connecting to an internal provisioning server, and it can be used externally connecting to an external provisioning server. Some commercial products use ZTP in connection with a vendor-controlled cloud-based provisioning server."
Funny, that's almost exactly what I said in my original response on this thread :)
Shall we collect items of OCP/OpenStack components that could composite a ZTP stack somewhere ?
Sure, just make sure we're being explicit about the things we're discussing. If you want to focus exclusively on *network device* provisioning, that's fine, but that should be explicitly stated.
Network device provisioning is an important but ultimately tiny part of infrastructure provisioning. Unfortunately, most of the telco and network OEM community (understandably) only refer to network device provisioning when they talk about "ZTP".
Also, the less this can be pidgeon-holed into the amorphous "edge" category, the better, IMHO ;)
Best, -jay
On Thu, Dec 20, 2018 at 10:51 PM Curtis <serverascode@gmail.com <mailto:serverascode@gmail.com>> wrote: On Thu, Dec 20, 2018 at 9:35 AM Jay Pipes <jaypipes@gmail.com <mailto:jaypipes@gmail.com>> wrote: On 12/20/2018 09:33 AM, Curtis wrote: > No, it doesn't do inventory management. It's like a small base OS for > network switches, they come with it, boot up into it, and you can use it > to install other OSes. At least that's how it's used with the whitebox > switches I have. With ONIE it'd install the OS, then the initial OS > could register with some kind of inventory system. What about for non-network devices -- i.e. general compute hardware? After all, edge is more than just the network switches :) I'm not sure; that's a good question. I was just using it as an example of a piece of ZTP related technology that has been adopted by vendors who build physical devices and include them by default, though of course, only a subset of network switches. :) If ONIE was a good example, and it could not be used for general compute hardware, then perhaps something like it could be built using lessons learned by ONIE. I dunno. :) Thanks, Curits Best, -jay -- Blog: serverascode.com <http://serverascode.com> -- Zhipeng (Howard) Huang Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com <mailto:huangzhipeng@huawei.com> Office: Huawei Industrial Base, Longgang, Shenzhen
-- Zhipeng (Howard) Huang Principle Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen
participants (4)
-
Curtis
-
Ildiko Vancsa
-
Jay Pipes
-
Zhipeng Huang