manageiq / guides Goto Github PK

The 5.3.2.5 is already telling me that sqlfilter is no longer used but it is not reflected in the REST guide.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

dnf is not currently available for CentOS 7. After speaking with some of the guys on Gitter/manageiq, it was talked about switching the documentation to advising CentOS users to use yum (at least, for now until dnf is made available again?).

Changes in #280 should be linked in https://github.com/ManageIQ/guides/blob/master/ui/rbac_features.md.

Also some other notes by @lpichler should be added. Waiting for more details.

@miq-bot assign @lpichler

I have been frustrated with our current override of the defaults for a while now, and have not been completely silent about it in the past:

ManageIQ/manageiq-providers-amazon#434 (comment)
ManageIQ/manageiq-providers-amazon#434 (comment)

And I don't think I am alone...

I would like to petition we change this back to the community styles.

(I also willingly take on the work to update our code bases to use this style, as this would very much ease a long standing "erk-some" I have had with it)

Reference links

• rubocop-hq style guide discussion: rubocop/ruby-style-guide#526
  • Case for change: http://www.chrisrolle.com/blog/ruby-percentage-notations
  • Case against change (one I disagree with): rubocop/ruby-style-guide#526 (comment)
• PR overriding the defaults: #286

There is a misunderstading on meaning of SSH keypair in add OpenStack Infra provider form. It is needed update docs to make clear that SSH keypair is not dependent on Non-SSL/SSL without validation/SSL choice in first panel.

See http://talk.manageiq.org/t/adding-an-openstack-infrastructure-provider/3684/2

https://docs.rubocop.org/rubocop/1.19/cops_naming.html#namingvariablenumber

This cop is annoying particularly in specs. What do you think about disabling entirely? I'm not sure what we really gain by keeping it except that it's noise.

Example PR that shows the bot complaining about it: ManageIQ/manageiq-providers-ibm_cloud#374, where it's complaining about these symbols: https://github.com/ManageIQ/manageiq-providers-ibm_cloud/pull/374/files#diff-d54a15a03812a47a8fca6738fa419467a30720611dd2f8bf976d99a120f8876eR35-R44

👍 Disable completely
👎 Keep as is
😕 Disable but only parts of it (such as only for symbols or only for method names)

The developer guide describes setting up a dev environment in CentOS 7, but the version of PostgreSQL provided is 9.2.

I was able to work around this by adding a PostgreSQL-provided repo.

The Containers Manager link is invalid in section: https://github.com/ManageIQ/guides/blob/master/architecture/providers_overview.md#provider-manager-types

Probably should be removed.

I'm using CentOS 7 and running through the developer setup instructions. When I get to bin/setup, it appears that some of the validation tests fail.

...
...
== Removing old logs and tempfiles ==

== Preparing tests ==
** Confirming rails environment does not connect to the database
** Preparing database
rake aborted!
PG::ConnectionBad: FATAL:  Ident authentication failed for user "user"
/home/erjohnso/manageiq/lib/tasks/evm_dba.rake:141:in `block (3 levels) in <top (required)>'
/home/erjohnso/manageiq/lib/tasks/test.rake:31:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:drop => db:check_protected_environments
(See full trace by running task with --trace)

So, I added --trace to the setup script and poked around my environment a bit. The last test, db:check_protected_environments, comes from a rails / active_record test suite.

I'm running PostgreSQL 9.2.14.

postgres=# \du
                             List of roles
 Role name |                   Attributes                   | Member of 
-----------+------------------------------------------------+-----------
 erjohnso  | Superuser                                      | {}
 postgres  | Superuser, Create role, Create DB, Replication | {}
 root      | Superuser                                      | {}

postgres=# \l
                                     List of databases
       Name       |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges   
------------------+----------+----------+-------------+-------------+-----------------------
 postgres         | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 template0        | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
                  |          |          |             |             | postgres=CTc/postgres
 template1        | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
                  |          |          |             |             | postgres=CTc/postgres
 vmdb_development | root     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 vmdb_test        | root     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
(5 rows)

Repeated bin/setup executions fail the same way. I can also repro the error if I run rake test:vmdb:setup.

Any thoughts or other info I can provide?

Thank you!

According to http://talk.manageiq.org/t/ruby-2-5-x-version-greater-than-2-5-3-is-the-only-supported-ruby-on-ivanchuk/4449, developers should now be using Ruby 2.5.x, so we should update this in the Requirements Summary at the top of the developer guide.

Several Style cops have moved to Layout and the configuration needs to updated accordingly. See ManageIQ/manageiq#16491

After the latest rebase on miq master, I noticed that required PostgreSQL version is now 9.5, but the documentation still says 9.4.
Please update the developer guide accordingly.
thanks!
cc @chessbyte @Fryguy

This link in readme is broken.

https://www.rdoproject.org/Deploying_RDO_using_Instack#Deploying_RDO_using_Instack

Using rbenv, and following the directions, bin/setup fails to properly configure the database.

Missing from the instructions are versions, almost none are listed.

I've burned almost two days on this already.

Here is the result of bin/setup:

== Migrating database ==
bower not-cached https://github.com/himdel/jquery.observe_field.git#~0.1.0
bower resolve https://github.com/himdel/jquery.observe_field.git#~0.1.0
bower not-cached https://github.com/himdel/spice-html5-bower.git#~1.6.3
bower resolve https://github.com/himdel/spice-html5-bower.git#~1.6.3
rails aborted!
LoadError: No such file to load -- environment_management
/home/jonz/RubymineProjects/manageiq/lib/extensions/as_include_concern.rb:54:in rescue in include_concern' /home/jonz/RubymineProjects/manageiq/lib/extensions/as_include_concern.rb:49:in include_concern'
/home/jonz/RubymineProjects/manageiq/app/models/miq_server.rb:8:in <class:MiqServer>' /home/jonz/RubymineProjects/manageiq/app/models/miq_server.rb:3:in <top (required)>'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:70:in my_server' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:39:in resource'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:60:in settings_holder' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:43:in load'
/home/jonz/RubymineProjects/manageiq/lib/patches/config_patch.rb:3:in reload!' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings.rb:59:in for_resource'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings.rb:18:in init' /home/jonz/RubymineProjects/manageiq/config/application.rb:140:in block in class:Application'
/home/jonz/RubymineProjects/manageiq/config/environment.rb:5:in <top (required)>' bin/rails:4:in require'
bin/rails:4:in <main>' LoadError: No such file to load -- miq_apache /home/jonz/RubymineProjects/manageiq/app/models/miq_server/environment_management.rb:1:in <top (required)>'
/home/jonz/RubymineProjects/manageiq/lib/extensions/as_include_concern.rb:51:in include_concern' /home/jonz/RubymineProjects/manageiq/app/models/miq_server.rb:8:in class:MiqServer'
/home/jonz/RubymineProjects/manageiq/app/models/miq_server.rb:3:in <top (required)>' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:70:in my_server'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:39:in resource' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:60:in settings_holder'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings/database_source.rb:43:in load' /home/jonz/RubymineProjects/manageiq/lib/patches/config_patch.rb:3:in reload!'
/home/jonz/RubymineProjects/manageiq/lib/vmdb/settings.rb:59:in for_resource' /home/jonz/RubymineProjects/manageiq/lib/vmdb/settings.rb:18:in init'
/home/jonz/RubymineProjects/manageiq/config/application.rb:140:in block in <class:Application>' /home/jonz/RubymineProjects/manageiq/config/environment.rb:5:in <top (required)>'
bin/rails:4:in require' bin/rails:4:in

The CFME docs have a section for what versions of providers are supported for each release of CFME. This would be helpful to have for ManageIQ as well.

I am new to Manage IQ and followed the instructions to create a provider.
When I click the link i am getting the 404 error.
http://manageiq.org/docs/guides/providers/generator/generator
Kindly provide the correct link to download the generator.

I couldn't start the installation with:
gem install bundler -v "~>1.7.4"

but it worked with:
gem install bundler -v "~>1.8.4"
(not sure what exact minimal version is necessary)

Then the "bundle install" command would fail on nokogiri-1.6.7 build, to pass that I had to do:
sudo dnf install rpm-build

The document developer_setup.md mentions the need of Ruby 2.2.2+ under the heading Install Ruby, but it does not give an example of what to do in case people are unfamiliar to the use of a version manager.

See https://rubydoc.info/gems/rubocop/0.69.0/RuboCop/Cop/Style/AccessModifierDeclarations

tl;dr

# group (default)
class Foo
  def method0
  end

  private

  def method1
  end

  def method2
  end
end

# inline
class Foo
  def method0
  end

  private def method1
  end

  private def method2
  end
end

I would like to disable this cop. I like inline modifiers, but this new cop is enforcing the group style. I don't think we have a preference collectively, so I'd like to disable it and allow for inline in addition to group.

Please vote with what you think.

👍 - allow developers to do both group and inline (disable the cop)
👎 - only support group, do not allow inline (leave it as is)
🚀 - only support inline, do not allow group (opposite than currently)

From discussion on SUI gitter room.

Since our upstream appliances are production mode, it would be nice to have directions for people to convert them to dev mode for rebuild purposes. For example, a user wants to change the skinning, but can't because we build the SUI with --production so the build bits are not there.

Update README.md to href-link to https://github.com/ManageIQ/manageiq-appliance-build

In the following guide Extending the UI with buttons, dialogs and executing Ansible Playbooks (https://www.manageiq.org/docs/guides/ui/provider_plugin).

The form example for React is broken - gives a 404:

The link is pointing to https://github.com/ManageIQ/react-ui-components/tree/master/src/amazon-security-form-group

Maybe should go here: https://github.com/ManageIQ/react-ui-components/tree/master/src/forms

• Rails style guide see https://github.com/bbatsov/rails-style-guide
• Bugzilla how-to
  • how to copy commit details / clone a ticket
• Git how-to
  • reword a commit
  • amend a commit
  • squashing
  • reordering
  • deleting a commit
  • uncommit a file from an existing commit
• Move CFME-specific stuff into CFME proper
  • logs
  • error collection
• Create CONTRIBUTING.md files on other open source projects that reference this guide. Mirror the one in CFME.

feature/add_abc_cloud
bug/typo_in_abc_cloud