Skip to content

Use number of fip also for internal network#428

Draft
jose-caballero wants to merge 2 commits intomainfrom
use_number_of_fip_also_for_internal_network
Draft

Use number of fip also for internal network#428
jose-caballero wants to merge 2 commits intomainfrom
use_number_of_fip_also_for_internal_network

Conversation

@jose-caballero
Copy link
Contributor

Description:

Special Notes:


Submitter:

Have you (where applicable):

  • Added unit tests?
  • Checked the latest commit runs on Dev?
  • Updated the example config file(s) and README?

Reviewer

Does this PR:

  • Place non-StackStorm code into the lib directory?
  • Have unit tests for the action/sensor and lib layers?
  • Have clear and obvious action parameter names and descriptions?

Use the number of FIPs specified in the user form for both the Externals
and the Internals Networks, and always override the default value.

For that, the FIP creation and allocation process has been moved to its
own dedicated function.
This new function is called even before checking which type of network is
involved in order to decide the correct function to use to set it up.
@jose-caballero jose-caballero marked this pull request as draft February 5, 2026 17:33
@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.81%. Comparing base (15d598e) to head (4af85dd).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #428   +/-   ##
=======================================
  Coverage   99.81%   99.81%           
=======================================
  Files         109      109           
  Lines        2640     2648    +8     
  Branches      331      331           
=======================================
+ Hits         2635     2643    +8     
  Misses          4        4           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jose-caballero jose-caballero force-pushed the use_number_of_fip_also_for_internal_network branch from 76e7b83 to 4af85dd Compare February 5, 2026 17:39
)
allocate_floating_ips(
conn,
network_identifier=network.value,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this will attempt to allocate floating IPs from the Internal network which we don't want, only from External or Jasmin

conn,
network_identifier=network.value,
project_identifier=project.id,
number_to_create=number_of_floating_ips,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will max out their quota when the project is created?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we should not do this. Let users allocate their own FIPs. Otherwise we are wasting FIPs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants