Skip to content
This repository has been archived by the owner on Jan 5, 2024. It is now read-only.

Standing Agenda, Public Core Meeting Meeting - November 2016 #140

Closed
abadger opened this issue Nov 8, 2016 · 13 comments
Closed

Standing Agenda, Public Core Meeting Meeting - November 2016 #140

abadger opened this issue Nov 8, 2016 · 13 comments

Comments

@abadger
Copy link
Contributor

abadger commented Nov 8, 2016

#Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.

If your IRC nick is different from your Github username, leave that as well.

See https://github.com/ansible/community/blob/master/MEETINGS.md for the schedule

Once an item has been addressed it should get strike-though ~~strike-though~~

@abadger
Copy link
Contributor Author

abadger commented Nov 8, 2016

From previous agenda ticket, @gundalow:

I'd like to float the idea of Ansible detecting passing invalid modes to file: (etc)
Not sure if by the time we parse that if we can tell if it's a number and if the leading zero has been dropped.

Discussed during 2016-11-10:

  • Has been thought about before
  • Would need to be done in a way that doesn't break anything
  • We can't think of any sensible way of doing this, so nothing to do here

@abadger
Copy link
Contributor Author

abadger commented Nov 8, 2016

From previous agenda ticket, @gundalow:

ansible/ansible-modules-core#5388 MySQL Security issue
from WouterOosterveld as something that should go into 2.2

Current status: jmainguy and WouterOosterveld are discussing in the ticket.

Discussed during 2016-11-10:

  • Not sure if this truly is a security issue @jctanner to contact kseifried
  • jmainguy to review PR

Discussed during 2016-11-15:

  • jmainguy will test on MySQL 5.7 and recommend merge or changes

Leaving item open so we can review next meeting

Jmainguy and WouterOosterveld are now happy that the change is ready to merge. jimi-c merged and backported to stable-2.1 and stable-2.2

@abadger
Copy link
Contributor Author

abadger commented Nov 8, 2016

How long to deprecate before removal: #139

Decided that current three release sequence is sufficient and not emitting deprecation notices doesn't make much sense for the majority of use-cases. Added a workaround if the user's site wants that workflow.

@gundalow
Copy link
Contributor

gundalow commented Nov 10, 2016

Fix YAML source and lint it

We already have yamllint (with some rules disabled), do we want to formalise that more?

ansible/ansible#15470

cc @adrienverge @mattclay

merged by mattclay

@gundalow
Copy link
Contributor

gundalow commented Nov 10, 2016

Proposal: ansible-config
ansible/proposals#35

Discussed (lots) during 2016-11-15:

continued discussion necessary

@gundalow
Copy link
Contributor

gundalow commented Nov 10, 2016

Module examples

< agaffney> I've found 57 instances throughout the source tree of with_(items|dict|indexed_items) and a bare variable

We happy to clear all of those out?
Do we need to add in detection for them?

Discussed during 2016-11-10:

  • agaffney has kindly offered to fix these
  • @gundalow and @mattclay need to review the ones in ansible/test

Discussed during 2016-11-15:

  • awaiting update/merge

@Shaps
Copy link

Shaps commented Nov 16, 2016

Discuss implementation of ansible/ansible#18501 - This is to be discussed in 2016-11-22 meeting.

@gundalow gundalow changed the title Standing Agenda, Public Core Meeting Meeting Standing Agenda, Public Core Meeting Meeting - November 2016 Nov 17, 2016
@gundalow
Copy link
Contributor

#143
Provides a document with lifecycle of the various releases

Discussed during 2016-11-17 Core meeting
We currently have

@gundalow
Copy link
Contributor

No Public Core Meeting on Thursday 24th November

@gundalow
Copy link
Contributor

gundalow commented Nov 25, 2016

From discussion in networktocode.
Can we provide better messages regarding missing dependencies. On a number of occasions users have been confused when told package foo isn't installed when it is. The actual issue being they are running in a virtual env

Can we have a few failure message that returns some extra state, e.g
self.dependency_fail('junos-eznc >= 1.2.2 is required but does not appear to be installed. It can be installed using 'pip install junos-eznc')

Would return something along the lines of
'msg:' 'ERROR: unos-eznc >= 1.2.2 is required but does not appear to be installed. It can be installed using 'pip install junos-eznc'. You are running inside sys.executable

If agreed we need to update the existing modules (and inventory scripts) as well as developing_modules.html

Update Discussed 29-Nov-2016 No definite conclusion but:

  • adding the information sounds good but talk to bcoca about whether we can add it controller-side.
  • we'd need to think more about an AnsibleModule method... might want to expand it to make conditional_importing better in general.

@gundalow
Copy link
Contributor

More details about upcoming repo merge
Important to review for those looking to contribute to module development https://groups.google.com/forum/#!topic/ansible-project/9WpXraBSLz8

@jctanner
Copy link
Contributor

jctanner commented Dec 1, 2016

Inability to find modules in subdirectories of "library" has been gaining more and more attention

ansible/ansible#15432

We need to decide if we'll accept a patch or not and then give guidance in the issue or close it.

@gundalow
Copy link
Contributor

gundalow commented Dec 8, 2016

It's now December so closing this

I've carried over

  1. Can we provide better messages regarding missing dependencies. On a number of occasions users have been confused when told package foo isn't installed when it is. The actual issue being they are running in a virtual env
  2. Inability to find modules in subdirectories of "library" has been gaining more and more attention

MEETING CLOSED

December's Agenda #147

@gundalow gundalow closed this as completed Dec 8, 2016
@dagwieers dagwieers added core and removed core labels Jun 24, 2017
@ansible ansible locked and limited conversation to collaborators Jul 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants