We currently don't show the capabilities in the UI. You could add that info to state.json though where we model the framework. Mind sending a patch for that?
Also, the requestReesources() call is currently a no op. @vinodkone > On Jun 18, 2015, at 8:06 AM, Aditi Dixit <[email protected]> wrote: > > Well currently there's only Revocable Resources right, so just that. > > To reiterate, I initially register a framework with the Revocable Resources > capability, and then reregister it without the Revocable Resources > capability. I want to verify that when reregistration happens, it does not > take into effect that the capability has been dropped after reregistration > and should keep offering revocable resources if asked by the framework. > > Ps. If the framework doesn't have the Revocable Resources capability, what > should happen if it requests revocable resources? >> On 18-Jun-2015 8:13 pm, "Alex Rukletsov" <[email protected]> wrote: >> >> Hi Aditi, >> >> what capabilities do you mean? >> >> On Thu, Jun 18, 2015 at 8:58 AM, Aditi Dixit <[email protected]> >> wrote: >> >>> Hi, >>> When I re-register a framework with an updated name, I know that the >>> FrameworkInfo gets updated, because I can see that on the Mesos web UI. >>> Similarly, is there a way to check if the framework has capabilities >>> through the user interface? >>> >>> Thanks! >>
