> + /** > + * @since 4.0 > + */ > + boolean areAlarmActionsEnabled(ManagedEntity entity) throws RuntimeFault, > RemoteException; > + > + /** > + * @since 4.0 > + */ > + void enableAlarmActions(ManagedEntity entity, boolean enabled) throws > RuntimeFault, RemoteException; > + > + Alarm createAlarm(ManagedEntity me, AlarmSpec as) throws InvalidName, > DuplicateName, RuntimeFault, RemoteException; > + > + List<Alarm> getAlarm(ManagedEntity me) throws RuntimeFault, > RemoteException; > + > + List<AlarmState> getAlarmState(ManagedEntity me) throws RuntimeFault, > RemoteException; > +}
A general comment about the API interfaces: Currently the domain model and interface signatures (including the thrown exceptions) are coupled to `vijava`. It is ok for this first implementation, but if the plan is to get rid of that dependency, when promoting the provider to the main repo, we should start thinking about having API interfaces that are not coupled to a concrete library and have a jclouds model. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/61/files#r18060516
