search

ansible / galaxy

Legacy Galaxy still available as read-only on https://old-galaxy.ansible.com - looking for the new galaxy -> https://github.com/ansible/galaxy_ng
Apache License 2.0
852 stars 331 forks source link

Support for more platforms in the meta file. #882

Open sbaerlocher opened 6 years ago

sbaerlocher commented 6 years ago

Feature Request

Use Case

In the platform information in galaxy_info only Windows Server 2012R2 is supported for Windows systems. Meanwhile there are also Windows 10 and Windows Server 2016 and soon Windows Server 2019. I would suggest to add the other Windows operating systems in galaxy_info platforms.

Proposed Solution

Added the possibility to specify version 10 and 2016 or 2019 respectively.

Example

galaxy_info:
  platforms:
    - name: Windows
      versions:
        - 10
        - 2016
        - 2019

Alternatives

N/A

Implementation

N/A

chouseknecht commented 6 years ago

@tima

It would be ideal if Galaxy no longer stored a list of valid platforms, and that we no longer asked users to maintain a static list of platforms in meta/main.yml.

Since we're thinking about asking users to provide tests using Molecule, I wonder if we could extract platform info from the test scenarios. Could also extract it from Zuul settings, I think, for cases like ansible-network, where Molecule is not used.

My thinking is that we ultimately want to the present to an Ansible content user the list of tested platforms, rather than the static, likely not actually CI tested list we present today.

tima commented 6 years ago

I get the problem and it is tricky. The static list is suboptimal especially when you take into consideration windows and networking and that list is declared intent that is not tested. Not every bit of content will have Zuul or molecule or whatnot to derive things from though. Even if they all did have tests, I'm not sure we could realistically run them all given the size and scope of Galaxy. Users will expect to continue to see the OS/platforms the content is intended to work. Need to think about the bigger picture some more here.

sbaerlocher commented 5 years ago

I find the list practical to filter in the Galaxy. I don't assume that an Ansible role from the Galaxy will work out of the box.

chouseknecht commented 5 years ago

@newswangerd

Platforms is a static list stored in the Galaxy database. The process for adding a new one is manual, undefined, and reactive. When a user complains and/or files an issue, we add a new platform. To see a list of available platforms, users must query the Galaxy API.

I would like to create a page in the UI where users can view/search existing platforms, and submit a request for us to add a new platform.

Daniel-Sanchez-Fabregas commented 5 years ago

Could you add the platforms mentioned in https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general_windows.html#create-an-ansible-inventory?

The OS that is created is based on the image set. The following images can be used:

  • jborean93/WindowsServer2008-x86
  • jborean93/WindowsServer2008-x64
  • jborean93/WindowsServer2008R2
  • jborean93/WindowsServer2012
  • jborean93/WindowsServer2012R2
  • jborean93/WindowsServer2016
chouseknecht commented 5 years ago

@Daniel-Sanchez-Fabregas

Done. You can view the Windows platforms here

sbaerlocher commented 5 years ago

How about Windows 8 or 10, respectively Windows 10 1803 and 1809? Do they get their own release name?

vnovichek commented 5 years ago

It would be great to add desktop Windows (8 and 10) to the list.

ppouliot commented 4 years ago

Would it be possible to add vyos and edgeos to the list of platforms?

ddimatos commented 3 years ago

Would it be possible to add:

If the forward slash is an issue then "zOS" or "z_OS" would suffice. We have been testing on z/OS.

o0-o commented 1 year ago

A quick look at that stable releases page for RouterOS makes the static list approach appear even more unsustainable...

https://mikrotik.com/download/archive

That said, I would like specify RouterOS support somehow in the meta file.

Another idea would be to have a current option for release/version. I suspect many people aim to maintain their roles for currently supported versions of any given OS. In cases where versions are released multiple times a year, it becomes very easy to forget to update the platform list for every role. Currently, I use all for this, but of course, I'm not actually testing on versions of operating systems that are no longer supported.

jamesosbourn commented 1 year ago

Could we get Windows Server 2022 added to the list of Windows server platform versions. This was releases a couple of years ago but has not been requested to be added to the list yet. As per the original request could Windows 10 and perhaps even Windows 11 be added. There are times when it would be nice to be able to configure these instance versions as well.