Create initial data for virtualization models

[candlerb]

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

• Python version: 3.5.2
• NetBox version: v2.2-beta1

Description

Simple enhancement: loaddata initial_data could include

• Initial cluster types: "Public Cloud", "vSphere", "oVirt", "libvirt", "lxd", "docker"
• Initial clusters: "Amazon EC2", "Google GCE" (of type "Public Cloud")
• New Device Role "VM Host"

Use case: makes it quicker to add your first VM when trying out Netbox. Then the minimal work is to create one VM in "Amazon EC2", or to create a cluster + VM.

[RyanBreaker]

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

[jeremystretch]

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

[darkstar]

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

[candlerb]

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

[Zorlin]

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

…

On Tue, Oct 17, 2017 at 3:40 PM, Brian Candler ***@***.***> 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 <#1491 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABTmrBD0TJJ59taGubJrABc0vEBeBJdKks5stFnvgaJpZM4PYu4H> .

[darkstar]

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.

[candlerb]

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.

[darkstar]

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

[RyanBreaker]

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.

[ktims]

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.

[RyanBreaker]

Added those two.

[candlerb]

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.

[jeremystretch]

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?

[rdegez]

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

[RyanBreaker]

Added.

[cimnine]

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?

[jeremystretch]

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

[RyanBreaker]

@cimnine I think it's already a bit extensive as it is, and it is only initial data that someone can optionally import, more or less as examples.

@jeremystretch If you're ready I'm ready, I think it's good.

[cimnine]

@RyanBreaker Yeah, I thought so minutes after I commented.

[jeremystretch]

Merged #1604