Change approach for setting resources in apps

Bug #1539617 reported by Proskurin Kirill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-mesos
Fix Released
Wishlist
Michal Rostecki

Bug Description

Right now we have json files with marathon app configuration.
Current setting of RAM and CPU in each is not production ready and each production may require different amount of resources per app. So I think it's bad idea to keep them hardcoded.

Maybe we should move it to configuration profiles, like:
"memcached": { 'RAM': 512, 'CPU': 1}

Angus Salkeld (asalkeld)
Changed in kolla-mesos:
assignee: nobody → Michal Rostecki (mrostecki)
status: New → Confirmed
milestone: none → mitaka-3
Changed in kolla-mesos:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-mesos (master)

Reviewed: https://review.openstack.org/280144
Committed: https://git.openstack.org/cgit/openstack/kolla-mesos/commit/?id=14c724aa05391fa7ccf1eee9f1147b2d15712313
Submitter: Jenkins
Branch: master

commit 14c724aa05391fa7ccf1eee9f1147b2d15712313
Author: Michal Rostecki <email address hidden>
Date: Mon Feb 15 11:15:43 2016 +0100

    Make Mesos resources configurable

    Configure "mem" and "cpus" settings via zookeeper. Settings
    provided in this commit aren't ideal, but the logic itself
    is implementend and easy to change.

    Closes-Bug: 1539617

    Change-Id: I7207eef5e39feb2f68a94ac585ff5c8763d86616

Changed in kolla-mesos:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.