Create initial data for virtualization models #1227

@RyanBreaker commented on GitHub (Oct 16, 2017):

Just submitted the above pull request adding these items. I can easily add more if anyone has any additional suggestions before @jeremystretch accepts it.

@RyanBreaker commented on GitHub (Oct 16, 2017): Just submitted the above pull request adding these items. I can easily add more if anyone has any additional suggestions before @jeremystretch accepts it.

adam commented

@jeremystretch commented on GitHub (Oct 16, 2017):

I'll leave this open for a couple days in case anyone has suggestions.

@jeremystretch commented on GitHub (Oct 16, 2017): I'll leave this open for a couple days in case anyone has suggestions.

adam commented

@darkstar commented on GitHub (Oct 17, 2017):

hmmm, how about CEPH & Kubernetes as cluster types? And MS Azure as additional initial cluster?

@darkstar commented on GitHub (Oct 17, 2017): hmmm, how about CEPH & Kubernetes as cluster types? And MS Azure as additional initial cluster?

adam commented

@candlerb commented on GitHub (Oct 17, 2017):

I wouldn't include Ceph because it's not a virtualization environment, it's a storage service (*). The others are fine.

(*) Maybe some people might want to model non-virtualization clusters as Netbox "cluster", but that wasn't what it was intended for

@candlerb commented on GitHub (Oct 17, 2017): I wouldn't include Ceph because it's not a virtualization environment, it's a storage service (*). The others are fine. (*) Maybe some people might want to model non-virtualization clusters as Netbox "cluster", but that wasn't what it was intended for

adam commented

@Zorlin commented on GitHub (Oct 17, 2017):

In my opinion clusters should be limited to Compute workloads in Netbox.

On Tue, Oct 17, 2017 at 3:40 PM, Brian Candler notifications@github.com
wrote:

I wouldn't include Ceph because it's not a virtualization environment,
it's a storage service (*). The others are fine.

(*) Maybe some people might want to model non-virtualization clusters as
Netbox "cluster", but that wasn't what it was intended for

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/1491#issuecomment-337145546,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABTmrBD0TJJ59taGubJrABc0vEBeBJdKks5stFnvgaJpZM4PYu4H
.

@Zorlin commented on GitHub (Oct 17, 2017): In my opinion clusters should be limited to Compute workloads in Netbox. On Tue, Oct 17, 2017 at 3:40 PM, Brian Candler <notifications@github.com> wrote: > I wouldn't include Ceph because it's not a virtualization environment, > it's a storage service (*). The others are fine. > > (*) Maybe some people might want to model non-virtualization clusters as > Netbox "cluster", but that wasn't what it was intended for > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/1491#issuecomment-337145546>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABTmrBD0TJJ59taGubJrABc0vEBeBJdKks5stFnvgaJpZM4PYu4H> > . >

adam commented

@darkstar commented on GitHub (Oct 17, 2017):

In my opinion clusters should be limited to Compute workloads in Netbox.

That seems like an arbitrary decision and is not the way I'm using NetBox right now. Any reason behind your opinion?
We have virtualized storage systems that look and act like regular Virtual Machines.

@darkstar commented on GitHub (Oct 17, 2017): > In my opinion clusters should be limited to Compute workloads in Netbox. That seems like an arbitrary decision and is not the way I'm using NetBox right now. Any reason behind your opinion? We have virtualized storage systems that look and act like regular Virtual Machines.

adam commented

@candlerb commented on GitHub (Oct 17, 2017):

We have virtualized storage systems that look and act like regular Virtual Machines.

Something that acts and looks like a Virtual Machine can be modelled as "Virtual Machine" - no problem with that.

However, a netbox "Cluster" is not a grouping of virtual machines; it's a grouping of virtualization hosts on which VMs can run. The database models the relation Virtual Machine : (runs-on) : Cluster

The issue raised was whether "Ceph" should be one of the options for "Cluster Type". I'd say no, because Ceph is not a virtualization platform; the database would let you mark VMs as executing on the Ceph cluster, which is not the case.

@candlerb commented on GitHub (Oct 17, 2017): > We have virtualized storage systems that look and act like regular Virtual Machines. Something that acts and looks like a Virtual Machine can be modelled as "Virtual Machine" - no problem with that. However, a netbox "Cluster" is not a grouping of virtual machines; it's a grouping of virtualization hosts on which VMs can run. The database models the relation `Virtual Machine` : `(runs-on)` : `Cluster` The issue raised was whether "Ceph" should be one of the options for "Cluster Type". I'd say no, because Ceph is not a virtualization platform; the database would let you mark VMs as executing on the Ceph cluster, which is not the case.

adam commented

@darkstar commented on GitHub (Oct 18, 2017):

@candlerb I agree with that. I think I was confused and actually meant something else but it doesn't matter ;)

@darkstar commented on GitHub (Oct 18, 2017): @candlerb I agree with that. I think I was confused and actually meant something else but it doesn't matter ;)

adam commented

@RyanBreaker commented on GitHub (Oct 19, 2017):

So do we want to add Azure as another cluster option? Otherwise, if someone uses one or the other, it would be a simple rename.

@RyanBreaker commented on GitHub (Oct 19, 2017): So do we want to add Azure as another cluster option? Otherwise, if someone uses one or the other, it would be a simple rename.

adam commented

2025-12-29 16:30:16 +01:00

@ktims commented on GitHub (Oct 20, 2017):

Azure should be added, as should HyperV as a cluster type.

There are too many possible types of clusters to list here. I would again advocate for this to be added to the Admin panel and let the user decide how to use it.

@ktims commented on GitHub (Oct 20, 2017): Azure should be added, as should HyperV as a cluster type. There are too many possible types of clusters to list here. I would again advocate for this to be added to the Admin panel and let the user decide how to use it.

adam commented

@RyanBreaker commented on GitHub (Oct 20, 2017):

Added those two.

@RyanBreaker commented on GitHub (Oct 20, 2017): Added those two.

adam commented

2025-12-29 16:30:22 +01:00

@candlerb commented on GitHub (Oct 20, 2017):

There are too many possible types of clusters to list here. I would again advocate for this to be added to the Admin panel and let the user decide how to use it

The cluster types are already user-editable. This ticket is just about creating sample data that can be preloaded at install time, like the pre-loaded set of Manufacturers and Platforms for example.

@candlerb commented on GitHub (Oct 20, 2017): > There are too many possible types of clusters to list here. I would again advocate for this to be added to the Admin panel and let the user decide how to use it The cluster types are already user-editable. This ticket is just about creating sample data that can be [preloaded at install time](https://netbox.readthedocs.io/en/stable/installation/netbox/#load-initial-data-optional), like the pre-loaded set of [Manufacturers and Platforms](https://github.com/digitalocean/netbox/blob/develop/netbox/dcim/fixtures/initial_data.json#L83) for example.

adam commented

@jeremystretch commented on GitHub (Oct 26, 2017):

If we're going to list AWS and Azure as cloud providers, I feel somewhat obligated to list DigitalOcean too, given that they are NetBox's sole sponsor. However, I'm also very sensitive to potential conflicts of interest, so I wanted to propose it here. Any objections?

@jeremystretch commented on GitHub (Oct 26, 2017): If we're going to list AWS and Azure as cloud providers, I feel somewhat obligated to list DigitalOcean too, given that they are NetBox's sole sponsor. However, I'm also very sensitive to potential conflicts of interest, so I wanted to propose it here. Any objections?

adam commented

@rdegez commented on GitHub (Oct 26, 2017):

Seems 100% fair to me and it's very nice of you to even ask, I would say!

@rdegez commented on GitHub (Oct 26, 2017): Seems 100% fair to me and it's very nice of you to even ask, I would say!

adam commented

@RyanBreaker commented on GitHub (Oct 26, 2017):

Added.

@RyanBreaker commented on GitHub (Oct 26, 2017): Added.

adam commented

@cimnine commented on GitHub (Oct 27, 2017):

Since libvirt and vSphere are there, may I suggest Xen and maybe kvm?
And since Docker and lxd are there, may I suggest Kubernetes and Docker Swarm?

@cimnine commented on GitHub (Oct 27, 2017): Since `libvirt` and `vSphere` are there, may I suggest `Xen` and maybe `kvm`? And since `Docker` and `lxd` are there, may I suggest `Kubernetes` and `Docker Swarm`?

adam commented

@jeremystretch commented on GitHub (Oct 27, 2017):

@RyanBreaker Thanks. Ping me when you want this merged.

@jeremystretch commented on GitHub (Oct 27, 2017): @RyanBreaker Thanks. Ping me when you want this merged.

adam commented